refactor(flags): centralize and simplify flag parsing logic #478
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #469
Applied changes based on Issue #469.
I’ve centralized all of our flag‐parsing logic into src/utils/flags.ts, and turned src/utils/prompt.ts into a thin re‐export so that there’s a single implementation of
extractPromptFlags
. Here’s what changed:PromptFlagOptions
interface and theextractPromptFlags
function (formerly living in prompt.ts) immediately below the existingparseFlags
.extractPromptFlags
andPromptFlagOptions
from./flags.js
, so consumers/importers are unaffected.All existing tests for
parseFlags
andextractPromptFlags
continue to pass without modification.Changes applied
src/utils/flags.ts
src/utils/prompt.ts
No other files or tests required changing—the refactor simply moved the implementation and left all imports/tests untouched. Let me know if you’d like any further tweaks!