Since ReForm depends on ReSchema, we should make ReSchema an internal module of ReForm. This is a breaking change and we should provide a migration guide from v11.0.2 to v12.0.0 explaining in detail (for now, probably on the release notes but we could include a section to the website docs) how to remove ReSchema and use ReSchema as an internal module of ReForm.
The steps for the migration:
Remove the ReSchema package from bsconfig.json and package.json
Update all modules that access ReSchema (the package) module directly to ReForm.ReSchema (and do the same for ReSchemaI18n, etc)
TODO
[x] Create internal modules (ReForm__ReSchema.res and ReForm__ReSchemaI18n.res)
[X] Expose internal modules with a module alias: ReForm__ReSchema → ReForm.ReSchema (the same for i18n, etc)
[x] Remove ReSchema from bsconfig.json and package.json
[x] Update modules that use ReSchema (package) to use the internal module
[ ] Archive ReSchema (repository and npm package) and add a deprecation note to the README file
Description
Since
ReFormdepends on ReSchema, we should make ReSchema an internal module of ReForm. This is a breaking change and we should provide a migration guide from v11.0.2 to v12.0.0 explaining in detail (for now, probably on the release notes but we could include a section to the website docs) how to remove ReSchema and use ReSchema as an internal module ofReForm. The steps for the migration:bsconfig.jsonandpackage.jsonReSchema(the package) module directly toReForm.ReSchema(and do the same forReSchemaI18n, etc)TODO
ReForm__ReSchema.resandReForm__ReSchemaI18n.res)ReForm__ReSchema→ReForm.ReSchema(the same for i18n, etc)bsconfig.jsonandpackage.jsonReSchema(package) to use the internal moduleReSchema(repository and npm package) and add a deprecation note to the README file