A configuration system stores nested keys as dot-separated paths, e.g. server.http.port. Due to careless string concatenation, a path may end up with leading dots, trailing dots, or repeated dots between segments (e.g. ..server..http.port.). You must normalize such a path: split it on ., drop every empty segment that results (from a leading dot, a trailing dot, or two or more dots in a row), and join the remaining segments back together with a single ..
Line 1: a string S consisting only of lowercase letters, digits, underscores, and dots. S may be empty (a blank line).
The normalized path. If every segment of S is empty (including when S itself is empty), print an empty line.
S ≤ 200S contains only characters from [a-z0-9_.]Example 1
Input
..server..http.port.
Expected
server.http.port
Explanation
Splitting on `.` gives empty segments around the doubled dots and at the start/end; dropping them and rejoining leaves `server.http.port`.
Example 2
Input
config
Expected
config
Explanation
There are no dots at all, so the single segment `config` is unchanged.
Ready to solve this?
Sign in to open the editor, run your code against the sample tests, and submit against the full test suite.
Sign in to solve →