Repository vs ContentTypes and Schemas

[gallayl]

The problem:

At the moment the generated classes (ContentTypes, Schemas, etc...) are bundled together with sn-client-js and tightly coupled with the Repository object. In that way we can not extend or add content types from different packages (e.g. if we want install the types from the Services, Webpages and our custom solution), the only way is to overwrite the whole ContentTypes library inside sn-client-js

Suggestion

In the future we should distribute ContentTypes in a different NPM package (see #67, e.g. @sensenet/content-services), maybe alongside with backend dependency releases and we should allow to add Content Types and Schemas

import { servicesContentTypes, servicesSchemas } from '@sensenet/content-services';
import { customerContentTypes, customerSchemas } from '../customer-related-stuff';
import { MyCustomizedRepository } from '../'

const myCustomizedRepository = new MyCustomizedRepository({
             // options
             ContentTypes: [servicesContentTypes, customerContentTypes],
             Schemas: [servicesSchemas, customerSchemas]
});

TBD

• Conflict between different packages and their content - Is it possible?

[gallayl]

The ticket is obsolete.

• Every TypeScript class can be used as a ContentType, they can be passed as a generic argument. We should talk about the distribution in another ticket and review the sn-client-cli functionality - Review sn-client-cli functionality sn-client-cli#62

• We should allow schemas to be reloaded from the repository at runtime - https://github.com/SenseNet/sn-client-js/issues/70