fez at least throws this warning when uploading a distribution whose META6.json contains "production": true or false:
=<< WARN: "production" in META is deprecated. Please create a .fez file with the json object
{"production":false}
to continue using this functionality after v53
I'm not sure if this deprecation is just a decision by fez, or if it does reflect a decision about META6.json in general. It could also be that the production setting was entirely fez-specific from the start: The Raku docs and roasts never mention it; in particular, it's absent in this example META6.json. (The diff in fez that introduced this deprecation warning 3 years ago doesn't give an explanation.)
Anyway, if the goal is for the META module to work completely smoothly with fez, it appears one would need to:
- Deprecate setting
production => False in META6 objects, and remove such lines from code examples
One might also
- create an option for META6 objects to include fez-specific settings, so that the
.fez file suggested in the warning could be generated from them as well. Perhaps using prefixed names for these attributes (e.g. __fez_production) and/or an adverb in the constructor. (Not sure if something like this is a good idea, though.)
fez at least throws this warning when uploading a distribution whose META6.json contains
"production": trueorfalse:I'm not sure if this deprecation is just a decision by fez, or if it does reflect a decision about META6.json in general. It could also be that the
productionsetting was entirely fez-specific from the start: The Raku docs and roasts never mention it; in particular, it's absent in this example META6.json. (The diff in fez that introduced this deprecation warning 3 years ago doesn't give an explanation.)Anyway, if the goal is for the META module to work completely smoothly with fez, it appears one would need to:
production => FalseinMETA6objects, and remove such lines from code examplesOne might also
.fezfile suggested in the warning could be generated from them as well. Perhaps using prefixed names for these attributes (e.g.__fez_production) and/or an adverb in the constructor. (Not sure if something like this is a good idea, though.)