Closed garrettjstevens closed 2 years ago
@kyostiebi The feature schema (and other schemas) are now in place on the main branch and ready for the modules.
New repo (Issue52) has been created and it contains:
Should we also pass assemblyId as GET parameter because the db may contain several assemblies?
@kyostiebi yes, we should. Also, I rebased that branch so that it didn't conflict with the changes on main and opened a PR so I could add some review comments: https://github.com/GMOD/jbrowse-plugin-apollo/pull/54
Start and End position changes are now handled in Apollo-shared -package. Also initial changeLog -schema has been created in ../apollo-shared/src/schemas/changeLog.schema.ts.
This is now updated so that it will come after #59, and does not include the features/getFeatures
range request.
This is now implemented in branch Issue52B.
This will have:
the MongoDB schema for featuresGET: /features/getFeatures?seq_id=chr1&start=1000&end=2000When retrieving features by range, top-level features with all their children are returned.When retrieving features by id, the features and any of its children are returned, but not any of its parent or sibling features.