Deprecate storeOptionsAsProperties - #2561
Merged
shadowspawn merged 2 commits intoJul 27, 2026
Merged
Conversation
shadowspawn
marked this pull request as ready for review
July 26, 2026 23:17
abetomo
approved these changes
Jul 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Prompted by suggestions from @43081j to (eventually) reduce size of Commander, I looked at
.storeOptionsAsProperties().Problem
This was added in Commander 7 to ease transition to the new version of Commander by reverting to the old behaviour to run legacy code. The new approach is working well. No need to keep it in main README. Eventually we might drop the behaviour.
Solution
ChangeLog
.storeOptionsAsProperties()