Closed achou11 closed 9 months ago
Also, wanted to get some thoughts on the following before implementing changes since it may just be my personal preference:
I find it a little confusing that a lot of the options give an example that's setting to a value that isn't the default. For example:
Not sure why, but if there's a default set for the option, I would expect the example to show that being the case.
Would be good to more explicitly note what fields are required vs optional. Can be achieved either with some annotation like (required)
or (optional)
and/or adding to the TS type for the relevant example e.g. android.handleTimezoneChanges ?: boolean = ...
There's also some inconsistency throughout the page where some of the options show a value being set and others where it doesn't - regardless of if the option is optional or not. Would be nice to make it more uniform
All great thoughts and agreed on all @achou11
(optional)
after it to be clear. But I could also see ?
optional chaining being clear as well. Whichever works and feels right to you I think would work - great point.We'll merge this one as nice corrections already and feel free to post followup on above, thank you!
Mostly includes fix for spelling and grammar but also includes some small aesthetic improvements to the markup (i.e. code block wrapping for some known commands/fields that are referenced)