Metarhia master #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* unify def\def.schema handling + always handle additional properties like `required` * fix validation `path` of errors PR-URL: metarhia#379
Co-authored-by: Timur Shemsedinov <timur.shemsedinov@gmail.com> PR-URL: metarhia#379
PR-URL: metarhia#381
PR-URL: metarhia#383
PR-URL: metarhia#386
Closes: metarhia#387 PR-URL: metarhia#386
PR-URL: metarhia#388
PR-URL: metarhia#396
Non breaking: - elegant syntax/format for custom types and internal types - custom types support - preprocessor to reduce Schema preprocess complexity - any kind of nested arrays, array of references metarhia#378 - nested schemas with Schema instances support - any level of complex nested types support - custom validate for field - changed validate for schema, simplified for user - all user's validate functions support 4 types of syntax: boolean return, throw Error, error message as string return and array of error messages - reserved words permitted in schema if kind provided - function fields stored in schema - shorthand required key for collections support `{ 'array?': 'string' }` - many relation now checks in runtime - model now loads projections at the end, to fix bug - schema kinds moved to separate file and kinds now have logic to remove hardcoded projection from Schema - ts interfaces from schema now have relation ids as well - deps update metautil - nested object support metarhia#395 - syntax for validate function changed Breaking: - Model no more require metavm for browser compatibility: need `impress` update - loadModel moved to loader: need `impress` update - Model no more writes d.ts file to disk moved to loader as well: need `metasql` update - syntax for pg types changed a bit, no more not-working types: need `metasql` update - not supporting custom Schema kinds: need to not use custom kinds in schemas folder: `application/schemas/<YourSchema.js>` PR-URL: metarhia#393
PR-URL: metarhia#399
PR-URL: metarhia#399
PR-URL: metarhia#400
Closes: metarhia#281 PR-URL: metarhia#402
Refs: metarhia#393 Refs: metarhia#402 PR-URL: metarhia#405
PR-URL: metarhia#406
PR-URL: metarhia#410
Co-authored-by: Timur Shemsedinov <timur.shemsedinov@gmail.com> PR-URL: metarhia#407
PR-URL: metarhia#412
PR-URL: metarhia#413
PR-URL: metarhia#414
PR-URL: metarhia#416
Test fixups from <metarhia@5732714>
PR-URL: metarhia#424
PR-URL: metarhia#424
…metarhia-master # Conflicts: # CHANGELOG.md # lib/schema.js # test/schema.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
npm t)npm run fmt)