René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"DSC config overwrites existing custom oh-my-posh PowerShell profile line","articleBody":"Hi team - thank you for sharing great config. I'm loving it!\n\nI found that the current WindowsDeveloperConfig DSC setup can overwrite an existing custom `oh-my-posh` initialization line in my PowerShell profile.\n\nFirst, I want to say I totally understand this project is intentionally **opinionated**, so using the default `oh-my-posh` setup is completely reasonable if that is the intended behavior. I’m opening this mostly because it was confusing to me at first that DSC was modifying only the `oh-my-posh` line in my PowerShell profile silently changing prompt, and I wanted to leave a note in case someone else runs into the same thing.\n\nI also fully admit my suggested workaround may be a bit over-engineered and potentially inefficient: using a separate script-based DSC resource to detect an existing `oh-my-posh` line, even though there is already a dedicated `OhMyPosh/Shell` DSC implementation, is not ideal on paper. However, based on the current behavior on both sides, it seems like this may be the only practical way to avoid overwriting an existing custom `oh-my-posh` setup.\n\n### Current behavior\n\nIn `windows-dev-config/dev-config.winget`, the config uses:\n\n```yaml\n- type: OhMyPosh/Shell\n  name: ohMyPoshProfileSet\n  dependsOn:\n    - OhMyPosh\n  properties:\n    states:\n      - name: pwsh\n        command: oh-my-posh init pwsh\n```\n\nWhen DSC is applied, it updates the existing `oh-my-posh` init line in `$PROFILE` to the declared command.\n\nThat means a custom line like:\n\n```powershell\noh-my-posh init pwsh --config \"$HOME\\.config\\oh-my-posh\\M365Princess.omp.json\" | Invoke-Expression\n```\n\ngets rewritten to:\n\n```powershell\noh-my-posh init pwsh | Invoke-Expression\n```\n\n### Why this is a problem\n\nMany users customize their prompt via `--config`, and this is valid/manual user configuration. The rest of the profile remains untouched, but the `oh-my-posh` line is normalized and the custom theme/config is lost.\n\n### Suggested change\n\nInstead of using `OhMyPosh/Shell` directly here, please consider using a script-based DSC resource that:\n\n- checks whether `$PROFILE` already contains any non-comment `oh-my-posh init` line\n- **skips modification if one already exists**\n- only appends the default `oh-my-posh init pwsh | Invoke-Expression` line when no existing `oh-my-posh` initialization is present\n\nThis would preserve existing user customization while still bootstrapping oh-my-posh for users who do not already have it configured.\n\n### Why I’m suggesting this on the WindowsDeveloperConfig side\n\nThe upstream `oh-my-posh` DSC resource currently rewrites the matched init line unless it already contains the exact canonical command string, so it does not preserve extra args like `--config`. I totally admit that writing separate script to check `oh-my-posh init` line is bit over-engineered and potentially inefficient.\n\n### Possible implementation direction\n\nA `Microsoft.DSC.Transitional/PowerShellScript` resource could use:\n\n- `testScript`: return `$true` if `$PROFILE` already contains a non-comment `oh-my-posh init` line\n- `setScript`: create `$PROFILE` if missing and append the default line only if no such line exists\n\n### Expected behavior\n\nIf the profile already contains any valid `oh-my-posh init` command, DSC should treat that as compliant and avoid modifying it.\n","author":{"url":"https://github.com/shunkino","@type":"Person","name":"shunkino"},"datePublished":"2026-06-03T04:12:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/53/WindowsDeveloperConfig/issues/53"}