-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ordered options #567
Comments
I think your proposal in mapbox/rio-color#23, plus the first solution (using non-space as delimiter) is much better. A "click-based" design also means to me that it wouldn't violate the strong opinions about semantics that come with Click (e.g. unordered options). Unsurprisingly I happen to agree with those opinions. What about this DSL:
This is still unambigous assuming all your filters accept a constant amount of args. With all that said, you can, in theory, preserve the order by subclassing |
@untitaker Thanks for the input - at least I can rest assured that I'm not missing something obvious in the click docs. Overriding The unquoted DSL approach might work very well, thanks for the suggestion! |
I'll close this then as there's nothing actionable. Good luck. |
I have a situation where I need to know the order of multiple multi-value options. i.e.
is different from
Is there any way to retain the order of the supplied options or is this outside of click's scope? Does anyone have any suggestions for different click-based designs that would accomplish the same task (short of writing a DSL)?
The text was updated successfully, but these errors were encountered: