Stream: committers
Topic: Removing Default Values
Grahame Grieve (Feb 24 2018 at 05:39):
@all I am removing default values from the current build. Here's my rough plan:
- the build tool will create an error any time default values are found
- I will go through and turn default values into meaning when missing
- I will also remove any trivial meaning when missing values
- I will let particular editors know if I think there's anything a little debatable about the decisions I make while doing this
Grahame Grieve (Feb 24 2018 at 05:40):
@Lloyd McKenzie can we enhance the report at the end of the build to list some or all todos for each resource?
Lloyd McKenzie (Feb 24 2018 at 05:51):
How would that be different from the existing warning (todo if you want FMM1+) & info messages (todo if you want FMM3+)
Grahame Grieve (Feb 24 2018 at 05:55):
because you can't add them without blowing up the build. I just think it would be good to add a note to editors - need to do X
Lloyd McKenzie (Feb 24 2018 at 06:03):
Well, if you add a new category of "todo", I can report it. (It might even report automatically)
Grahame Grieve (Feb 24 2018 at 06:03):
add it where?
Grahame Grieve (Feb 24 2018 at 07:15):
@Richard Ettema I have changed TestScript to remove default values. For TestScript, I have just made all the elements required
Lloyd McKenzie (Feb 24 2018 at 15:06):
ValidationMessage.IssueSeverity
Richard Ettema (Feb 25 2018 at 00:39):
@Grahame Grieve Understood. Thank you.
Last updated: Apr 12 2022 at 19:14 UTC
