Code Room
CodingMediumcod-g1503
Subject Config parsingLevel Entry–Mid~15 minCommon in Algorithms & data structures interviewsIndustries Software development

Question

A CI pipeline defines variables as lines of the exact form "KEY=value" (no comments, keys need no trimming; split on the first "="). A value may embed placeholders written as "${NAME}". Resolve every placeholder exactly once: substitute the RAW value of that key as written in the file — do not re-resolve anything inside the substituted text. A placeholder naming a key that does not exist becomes the empty string. A "${" with no closing "}" is kept verbatim through the end of the value, and a "$" not followed by "{" is ordinary text. Return the dict of resolved values.

Implement
resolve_placeholders(lines: list[str]) → dict[str,str]
Examples
in[["HOST=db.local","URL=postgres://${HOST}:5432"]]out{"URL":"postgres://db.local:5432","HOST":"db.local"}
What a strong answer looks like

State your approach and its time/space complexity out loud before you optimize. Handle the edge cases (empty input, duplicates, overflow), and say why you chose this over the brute force. Green tests are the floor, not the grade.

Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.

Run or narrate your approach, then ask the coach.