search

jkHCBB / validator

0 stars 0 forks source link

Strict optional handling. #1

Open ethanLhciactive opened 3 months ago

ethanLhciactive commented 3 months ago

Was wondering if you had implemented a strict option that detects if an optional attribute has been spelled incorrectly.

jkHCBB commented 3 months ago

Currently the tool is using the same exact schema that CMS is using, So if the schema would pick that up then the tool should as well. If you have an example, I can try to get something in place but no promise it will happen this week. I built this for the sole purpose of reporting back all of the errors that the cms validator would fail an MRF for, so I never changed what it looks for.

jkHCBB commented 3 months ago

So to answer your question, If say plan_name was spelled plane_nam it would still pass

ethanLhciactive commented 3 months ago

yes that's accurate, or as an example from my file, "billing_code_modifier" is spelled "billing_code_modifiers" which when used with the -strict tag on the cms tool, would be flagged as an error.