Releases: TranslatorSRI/Plater
Release v2.0.2
Trying to fix async event loop issue
Release v2.0.1
New transpiler version with a bug fix where edges without ids broke bolt results
Fixed SKIP LIST bug in plater
Release v2.0.0
- migrated to neo4j 5 w/ support for bolt or http protocols
- updated reasoner pydantic models
- moved most of the attribute handling logic to reasoner-transpiler
- added workflow for releasing neo4j images to the github container registry
- using OTLP exporter/protocol instead of jaeger client
Release v1.6.5 no-cypher
v1.6.5 with the /cypher endpoint disabled
Release v1.6.5
This release includes a fix for a bug where removing the TRAPI version prefix from api endpoints caused some attributes to be missing from the open api spec.
Release v1.6.4
This release includes new versions of reasoner-transpiler and subsequently bmt, and fixes a bug related to invalid subclass_depth configurations.
Release v1.6.3
Changed /simple_spec so that it uses the meta kg, and not a cypher call, to generate the entire simple_spec when no nodes are specified. It also caches the result so that it doesn't have to generate it again.
Release v1.6.2
Removed /overlay endpoint and improved some descriptions for openapi
Release v1.6.1
Refactoring the consolidation of the /1.4/ and / sub-applications, cleaning up redundancies
Release v1.6.0
TRAPI 1.5 implementation
- removed /1.4/ part of path from the endpoints
- changes to support set_interpretation instead of is_set (with an error for a value of "MANY")
- some changes to attribute handling, now use the biolink model to attempt to determine attribute types and values but also look at the custom mappings
- use bmt to determine whether a property is a qualifier or not
Implementation of new parameters for the /query endpoint:
- profile (boolean) will cause the endpoint to return SpeedScope profiling results instead of an answer
- validate (boolean) will cause Plater to validate the result using the pydantic model
Implementation of new optional config/env vars:
- RESULTS_LIMIT can apply a limit on the number of results returned by /query queries
- SUBCLASS_DEPTH will specify the number of hops allowed for subclass inference