The requiredAsync reference with this PR is a bit different from the required reference on the website. After this PR is merged, I'll make sure to update the required reference (if there are any changes needed). Here are the differences along with the reasons:
The required reference does not use a type parameter for the message parameter but the requiredAsync reference does. I think we should list TMessage so that:
a. the reference is as close to the code as possible.
b. we display the link between the message parameter and the output schema in the reference.
The naming of the output schemas. Instead of naming the output Schema, it is better to name the schemas AllKeysSchema and SelectedKeysSchema so that readers can identify the schemas in the 'Returns' section.
The
requiredAsync
reference with this PR is a bit different from therequired
reference on the website. After this PR is merged, I'll make sure to update therequired
reference (if there are any changes needed). Here are the differences along with the reasons:The
required
reference does not use a type parameter for the message parameter but therequiredAsync
reference does. I think we should listTMessage
so that: a. the reference is as close to the code as possible. b. we display the link between themessage
parameter and the output schema in the reference.The naming of the output schemas. Instead of naming the output
Schema
, it is better to name the schemasAllKeysSchema
andSelectedKeysSchema
so that readers can identify the schemas in the 'Returns' section.