Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate the Grakn schema creation from loader to API #25

Closed
manonviallet opened this issue Apr 17, 2019 · 1 comment
Closed

Migrate the Grakn schema creation from loader to API #25

manonviallet opened this issue Apr 17, 2019 · 1 comment
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@manonviallet
Copy link
Contributor

manonviallet commented Apr 17, 2019

Problem to Solve

Currently, the Grakn schema is created by the JAVA loader. Since this loader is deprecated and to be more consistent, the Grakn schema must be created by a NodeJS command on the API side.

Current Workaround

None.

Proposed Solution

Implement a command in the NodeJS API to create the Grakn schema.

Additional Information

None.

@SamuelHassine SamuelHassine added this to the 1.0-beta milestone Apr 20, 2019
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Apr 20, 2019
@SamuelHassine SamuelHassine changed the title Migrate the schema from loader to API Migrate the Grakn schema creation from loader to API Apr 20, 2019
@SamuelHassine
Copy link
Member

The command schema has been implemented.

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 20, 2019
@SamuelHassine SamuelHassine modified the milestones: v1.0.0-beta, v1.0.0 Jun 17, 2019
@SamuelHassine SamuelHassine reopened this Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

3 participants