Maria José Solano d9a00a876b Change type of flag defaults to Option<Value> (#9085) ... # Description Follow-up of #8940. As @bobhy pointed out, it makes sense for the behaviour of flags to match the one for positional arguments, where default values are of type `Option<Value>` instead of `Option<Expression>`. # User-Facing Changes The same ones from the original PR: - Flag default values will now be parsed as constants. - If the default value is not a constant, a parser error is displayed. # Tests + Formatting A [new test](e34e2d35f4/src/tests/test_engine.rs (L338-L344)) has been added to verify the new restriction.		2023-05-03 23:09:36 +02:00
..
deparse.rs	Use variable names directly in the format strings (#7906)	2023-01-29 19:37:54 -06:00
eval.rs	allow register to accept a const argument (#8758)	2023-04-08 15:04:57 -05:00
flatten.rs	Relax the closure syntax, highlight differently (#8846)	2023-04-12 05:21:52 +12:00
known_external.rs	Document and critically review ShellError variants - Ep. 3 (#8340)	2023-03-06 18:33:09 +01:00
lex.rs	Fix strange error on unbalanced curly braces (#8906)	2023-04-17 21:51:10 +12:00
lib.rs	Refactor to support multiple parse errors (#8765)	2023-04-07 12:35:45 +12:00
lite_parser.rs	Refactor to support multiple parse errors (#8765)	2023-04-07 12:35:45 +12:00
parse_keywords.rs	Fix overlay's help message lead to internal error (#9087)	2023-05-03 14:08:54 +03:00
parse_patterns.rs	Remove old alias implementation (#8797)	2023-04-07 21:09:38 +03:00
parser.rs	Change type of flag defaults to Option<Value> (#9085)	2023-05-03 23:09:36 +02:00
type_check.rs	allow records to have type annotations (#8914)	2023-04-26 08:16:55 -05:00