Change format keyword positioning
What kind of change does this PR introduce?
PR moves the format section of the documentation from the misplaced string page to under the more generic type as discussed in Issue #759. Which aims to remove the Misinterpretation that the reader might get that format as a keyword is only for string types which is not the case.
Also, Add further clarification that format as a keyword is generic. Using these lines added further
Issue Number:
- Closes #187
Screenshots
- Added section under type page
- removed from
formatsection from string page
Summary
PR aims to re-adjust the positioning of format keyword definitions. To remove any confusion of it being a string specific keyword as reported by the users here Slack Archives
Does this PR introduce a breaking change? No
CC - @benjagm @gregsdennis @jviotti
misplaced string page to under the more generic type as discussed in https://github.com/json-schema-org/json-schema-spec/issues/759
I checked the issue https://github.com/json-schema-org/json-schema-spec/issues/759 and it was closed 2019. Are you sure you are referring to the right issue?
Hello, I followed the Microsoft style guide for technical writing to review the content. My only concern is formatting the code snippets. If you are fixing the code snippet indentation here, It would help if you also fixed the indentation across the entire documentation.
Hello! :wave:
This pull request has been automatically marked as stale due to inactivity :sleeping:
It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.
There can be many reasons why a specific pull request has no activity. The most probable cause is a lack of time, not a lack of interest.
Let us figure out together how to push this pull request forward. Connect with us through our slack channel : https://json-schema.org/slack
Thank you for your patience :heart:
This issue is going to be closed due to inactivity.