-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SemanticErrorException when path key exceeds 1023 characters #95
Comments
Nope, according to YAML specs 1.2.2
|
OK, thanks for that pointer. So it seems that even though JSON does not have a limitation in the spec on key size (that I could find), I did find a reference that parser implementations could set a limit. To summarize my case:
Would it be possible to have this limitation be configurable so that the consumers of SharpYaml (like OpenAPI.NET) could pass in or otherwise set a higher limit? |
Yes. PR Welcome. |
Using v1.8.0.0 (via OpenAPI.NET v1.2.3) to parse an OA3 json document, we are seeing a SemanticErrorException when one of the keys in the Paths collection exceeds 1023 characters. For example, take the PetStore reference OA3 json and change the /pets path key to be extremely long. Attempt to read/parse the file, and get this exception:
(Edit: updated exception stack trace to include line numbers)
Here is the sample code that demonstrates this:
Here is the sample (long) path entry in the json file:
Our expectation is that keys of arbitrary lengths could be parsed. Is there a workaround for this apparent limitation?
The text was updated successfully, but these errors were encountered: