This repository has been archived by the owner on Jan 27, 2022. It is now read-only.
Rename codec keyword to parser
#241
Assignees
Labels
Comments
stencila-ci
added a commit
that referenced
this issue
Jan 23, 2021
# [1.0.0](v0.47.2...v1.0.0) (2021-01-23) ### Bug Fixes * **Helpers:** Account for change in directory ([4b0e079](4b0e079)) * **JSON Schemas:** Fix the base URL for "types schemas" ([10e9b35](10e9b35)), closes [#238](#238) * **Package:** Export JsonSchema type ([e328278](e328278)), closes [#240](#240) * **R:** Update NAMESPACE file ([aec2b25](aec2b25)) ### Code Refactoring * **Parser keyword:** Rename `codec` keyword to `parser` ([de26e9f](de26e9f)), closes [#241](#241) ### BREAKING CHANGES * **Parser keyword:** Renaming of `codec` keyword to `parser` will break existing validation / coercion.
|
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The custom
codeckeyword is useful but a little too closely linked to concepts in Encoda and also inaccurate (because it is never used to encode back to a string). Usingparseras the keyword is probably more understandable and in a similar vein to existing keywords in JSON Schema standard such asformatandpattern.The text was updated successfully, but these errors were encountered: