Replies: 3 comments
-
The best solution to this problem might actually a code style convention for Annatto (maybe even some kind of doc string template for fields) that forces contributors to mention TYPE and IS_REQUIRED (or whatever) in the doc string. Parsing field types and even worse, figuring out if they are required, seem to be sth undesirable in a language like Rust. |
Beta Was this translation helpful? Give feedback.
-
Another approach to think about a little bit is to refrain from using defaults for deserializable struct fields except for |
Beta Was this translation helpful? Give feedback.
-
The current policy is to enforce default. Where defaut is not possible for fields, use Option |
Beta Was this translation helpful? Give feedback.
-
The
info
function so far provides:This should be extended to avoid overloading the description with information that could be derived automatically. This includes:
Adding these will help keep frustration by trial and error low.
Beta Was this translation helpful? Give feedback.
All reactions