feat: enable allowUnknownFlags for specific commands #4921
Merged
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.
π Linked issue
β Type of change
π Description
According to the AdonisJS documentation, commands can accept unknown flags, which can be used in stubs to customize behavior such as output destination.
However, by default, the allowUnknownFlags option is disabled, preventing this feature from working as intended.
This PR enables the allowUnknownFlags option for specific commands that benefit from accepting and using additional flagsβrestoring alignment with the documented behavior. This is useful when using modular architecture.
If this PR is approved and merged, similar changes will be proposed for other packages like Lucid, Mail, and so on.(Edit: It appears that other packages have already enabled this option for make commands)π Checklist