This repository has been archived by the owner on Mar 1, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Provide more FLG directives. Don’t sort the whole list of lines at the end to keep the directives more in the order we want.
- Loading branch information
Showing
2 changed files
with
92 additions
and
24 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
52f5f57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand why the
safe_string
and co. are now both optional and of typeunit option
. Is it a way to disable an option that might be set in some component (and that would therefore be picked for themerlin
file)? If so, how about introducing a type like[ `yes | `no | `auto ]
for such arguments, with default at`auto
?52f5f57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your interpretation is correct:
Some (Some ())
means set the option.Some None
means don't set the option.None
means use a heuristic to set the option.I agree this is confusing but the benefit is that the inner
unit option
type is the same as the type of the corresponding fields in alib
orapp
. If we use[ `yes | `no | `auto ]
, I'd be inclined to replaceunit option
everywhere with[ `yes | `no ]
, but I'm not sure that is better. Theunit option
type is rather intuitive to represent the type of a command line flag that can be given or not.Would better documentation resolve the matter? What if we simply added the above explicit list of values and their meanings.
52f5f57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is rather a cosmetic motivation, to be fair. I think what would make the best sense to me would be
[`yes | `no] option
, whereSome `yes
would mean put the option,Some `no
don't put it andNone
leave the default is the underlying tool. But again, my point is really cosmetic only. There's nothing here that documentation couldn't fix.52f5f57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added for consideration in #62.