Json api entity provider for entity store.
npm install @dipscope/json-api-entity-provider!GitHub !NPM !Contributor Covenant
JsonApiEntityProvider.TS is an implementation of EntityProvider for EntityStore.TS package. You can find detailed information on the project page.
If you like or are using this project please give it a star. Thanks!
* What issues it solves?
* Installation
* Configuration
* Relationship operations
* To-One relationship provider
* To-Many relationship provider
* Versioning
* Contributing
* Authors
* Notes
* License
JsonApi entity provider aims to cover JSON:API specification. It supports the latest stable version (v1.1) and allows you easily connect to any backend API which follows described conventions. Besides it provides you extension points for different filtering and pagination strategies which might be used by a server.
JsonApiEntityProvider.TS is available from NPM, both for browser (e.g. using webpack) and NodeJS:
``
npm i @dipscope/json-api-entity-provider
_This package is a plugin for EntityStore.TS package. Please read documentation after installation. Besides you have to read documentation for TypeManager.TS to know all available options to configure your entity types._
First step is to create a provider and pass options you want to apply.
`typescript
import { JsonApiEntityProvider, JsonApiEntityProviderOptions } from '@dipscope/json-api-entity-provider';
import { JsonApiNetFilterExpressionVisitor, JsonApiNetPaginateExpressionVisitor } from '@dipscope/json-api-entity-provider';
import { AppEntityStore } from './app';
// Create entity provider.
const jsonApiEntityProvider = new JsonApiEntityProvider({
baseUrl: 'http://localhost:20001', // Url to you backend endpoint.
// Next options are optional...
jsonApiRequestInterceptor: (request: Request) => request, // You might intercept requests by adding headers.
jsonApiResponseInterceptor: (response: Response) => response, // You might intercept response by logging errors.
jsonApiFilterExpressionVisitor: new JsonApiNetFilterExpressionVisitor(), // You might override filtering strategy used by a server.
jsonApiPaginateExpressionVisitor: new JsonApiNetPaginateExpressionVisitor(), // You might override pagination strategy used by a server.
// Other options to override...
});
// Create entity store.
const appEntityStore = new AppEntityStore(jsonApiEntityProvider);
`
As JSON:API specification is agnostic about filtering and pagination strategies, you might need to select one of existing visitors or implement your own by extending base classes.
Second step is to define resource configuration for your entities as required by JSON:API specification. For the full list of available options check documentation for TypeManager.TS.
`typescript
import { Type, Property } from '@dipscope/type-manager';
import { EntityCollection } from '@dipscope/entity-store';
import { JsonApiResource } from '@dipscope/json-api-entity-provider';
import { Company, Message } from './app/entities';
@Type()
@JsonApiResource({
type: 'user' // Specify resource type.
route: 'users' // Custom route for the resource. If not specified, the value of type will be used.
})
export class User
{
@Property(String) public id?: string;
@Property(String) public name: string;
@Property(String) public email: string;
@Property(Company) public company: Company;
@Property(EntityCollection, [Message]) public messages: EntityCollection
// Omitted for brevity ...
}
`
The same configuration can be rewritten using declarative style.
`typescript
import { TypeManager, TypeMetadata, TypeConfiguration } from '@dipscope/type-manager';
import { EntityCollection } from '@dipscope/entity-store';
import { JsonApiResourceMetadata } from '@dipscope/json-api-entity-provider';
import { Company, Message } from './app/entities';
export class User
{
public id?: string;
public name: string;
public email: string;
public company: Company;
public messages: EntityCollection
// Omitted for brevity ...
}
export class UserConfiguration implements TypeConfiguration
{
public configure(typeMetadata: TypeMetadata
{
typeMetadata.configureTypeExtensionMetadata(JsonApiResourceMetadata)
.hasType('user')
.hasRoute('users');
typeMetadata.configurePropertyMetadata('id')
.hasTypeArgument(String);
typeMetadata.configurePropertyMetadata('name')
.hasTypeArgument(String);
typeMetadata.configurePropertyMetadata('email')
.hasTypeArgument(String);
typeMetadata.configurePropertyMetadata('company')
.hasTypeArgument(Company);
typeMetadata.configurePropertyMetadata('messages')
.hasTypeArgument(EntityCollection)
.hasGenericArguments([Message]);
return;
}
}
TypeManager.applyTypeConfiguration(User, new UserConfiguration());
`
After that you have to follow EntityStore.TS documentation. Supported methods which you can use through EntitySet is dependent from backend implementation of JSON:API specification.
The JsonApiEntityProvider supplies functionality for simplifying relationship operations.
NOTE: each of these operations assume that all entities are already stored.
Thus, operations to Update/Add models will have to performed after adding the related model to the entity set.
`typescript
const specEntityStore = new SpecEntityStore();
const userSet = specEntityStore.userSet;
const messageSet = specEntityStore.messageSet;
const companySet = specEntityStore.companySet;
const jsonApiEntityProvider = specEntityStore.jsonApiEntityProvider;
// Populate entity set.
const user = await userSet.add(user);
const company = await companySet.add(new Company());
const company2 = await companySet.add(new Company());
const newMessage = await messageSet.add(new Message());
const newMessages = await messageSet.bulkAdd([new Message(), new Message()]);
// Now perform relationship operations...
`
The To-One relationship provider enables operations on to-one relationships. To-One relationship provider currently only provides support for the following features:
1. Fetching related data.
2. Updating related data by pointing relationship to a different model.
3. Removing related data.
`typescript
const userCompany = jsonApiEntityProvider.createJsonApiToOneRelationship(userSet, user, u => u.company);
// Fetching To-One relationship data.
const company = await userCompany.find();
// Updating To-One relationship data.
await userCompany.update(otherCompany);
// Removing To-One relationship data.
await userCompany.remove();
`
The To-Many relationship provider enables operations on to-many relationships. To-Many relationship provider currently only provides support for the following features:
1. Fetching related data.
2. Fetching related data with include and sort clauses.
3. Fetching related data with pagination.
4. Adding an element to the related data.
5. Updating related data by pointing relationship to a different model.
6. Removing an element from the related data.
7. Saving non-root entities directly under their parent.
`typescript
const userMessages = jsonApiEntityProvider.createJsonApiToManyRelationship(userSet, user, u => u.messages);
// Fetching To-Many relationship data.
const messages = await userMessages.findAll();
// Fetching related data with include clauses.
const messagesWithUser = await userMessages.include(x => x.user).findAll();
const messagesWithReplies = await userMessages.includeCollection(x => x.messages).findOne();
// Fetching related data with sort clauses.
const messagesAsc = await userMessages.sortByAsc(x => x.text).findAll();
const messagesDesc = await userMessages.sortByDesc(x => x.text).findAll();
// Fetching related data with pagination clauses.
const firstPageData = await userMessages.paginate(x => x.pageSize(1, 10)).findAll();
const secondPageData = await userMessages.paginate(x => x.pageSize(2, 10)).findAll();
const lastPageData = await userMessages.paginate(x => x.pageSize(4, 10)).findAll();
// Adding element(s) to the related data.
await userMessages.add(newMessage);
await userMessages.bulkAdd(newMessages);
// Updating To-Many relationship data.
await userMessages.update(addedMessage);
await userMessages.bulkUpdate(addedMessages);
// Removing To-Many relationship data.
await userMessages.remove(addedMessage);
await userMessages.bulkRemove(toRemoveMessages);
// Saving non-root element(s) directly to their related parent.
await userMessages.save(newMessage);
await userMessages.bulkSave(newMessages);
``
We use SemVer for versioning. For the versions available, see the versions section on NPM project page.
See information about breaking changes, release notes and migration steps between versions in CHANGELOG.md file.
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
Dmitry Pimonov - Initial work* - dpimonov
See also the list of contributors who participated in this project.
Thanks for checking this package.
Feel free to create an issue if you find any mistakes in documentation or have any improvements in mind.
We wish you good luck and happy coding!
This project is licensed under the Apache 2.0 License - see the LICENSE.md file for details.