Improve field value parsing by adding `NoDecode` and `ForceDecode` annotations #492

👏 No style guide issues found.

1 files reviewed, no outstanding issues found.

Line	Issues	Text	Comment
377	(Spelling-error) Did you really mean 'validator'?	Existing: `this behavior for a field and parse the value in your own validator, you can annotate the field with`	The term 'validator' is a common term in programming and is used correctly in this context. The style guide review process likely flagged it incorrectly as a spelling error. No change is needed.
404	(Spelling-error) Did you really mean 'validator'?	Existing: 1. The `NoDecode` annotation disables JSON parsing for the `numbers` field. The `decode_numbers` field validator	The term 'validator' is correct in this context as it refers to a common programming concept. The style guide's suggestion to change it is a false positive. No change is needed.
435	(Spelling-error) Did you really mean 'config'?	Existing: This will bypass the `enable_decoding` config setting:	The term 'config' is a widely accepted shorthand for 'configuration' in technical contexts, especially when referring to settings or files. Therefore, the suggestion to change it is unnecessary, and the original text should remain unchanged.
466	(Spelling-error) Did you really mean 'validator'?	Existing: `and we have to provide a custom validator to parse the value.`	The term 'validator' is correctly used and spelled in the context of the sentence. The style guide's suggestion is a false positive, so no change is needed.

Hyperlint is your AI-powered copilot for creating high-quality documentation with minimal effort.

Sign up for a free plan at hyperlint.com.