-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create model #59
Merged
Merged
Create model #59
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
…y, Ontology, Property, Class, Individual
…y, Ontology, Property, Class, Individual according to OLS4 (api/v2) response structure
…hing, Entity, Ontology, Property, Class, Individual according to legacy (ols3/api, ols4/api/) response structure
…pi.ts which requests a response for given parameters and returns the respective model object containing the response
…t() inside EntityInfoWidget to get Entity / Ontology information via object methods. Widget JSX is now generated via methods extracting the different sections
… JSX for basic model structures (i.e. Reification)
…element for Reified axioms
…, still to be reviewed
…/ "term" for new API
…s4/api which does not have "annotations" key inside "config"
…e functionality with the v2 API
…er" property, added new functions for api calls in OlsApi.ts; OlsApi.ts and widgets have to be reviewed for errors
…value of useLegacy now automatically adds "v2/" to the api-URL if true.
…ectly; also changed display of defining ontology not available warning in some widgets
…rring using legacy API via parallel queries for all types
…sing useLegacy parameter
…xpressions and added onDataType; added function to render Tooltip with specified text
…risticsSection(), getDomainSection(), getRangeSection() and getIndividualPropertyAssertionsSection() to display the respective sections (as done in ols4 project)
…es both API versions
…SearchResultProps type
- instances API route is only available with ontologyId provided, so the ontologyId is provided through the entities' response object if props.ontologyId is not provided
… response is not an array
… out in annotations
… union type instead of string now
- new API does not accept unknown url parameters
- new API does not accept unknown url parameters
🎉 This PR is included in version 1.20.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Major update of the data model based on the OLS4 data model and HierarchyWidget improvements.