/bioentity/function/<id> conflict with /bioentity/<type>/<id>

monarch-initiative / biolink-api

API for linked biological knowledge

https://api.monarchinitiative.org/api/

BSD 3-Clause "New" or "Revised" License

63 stars 25 forks source link

Open deepakunni3 opened 5 years ago

deepakunni3 commented 5 years ago

The route /bioentity/function/<id> hides the ability to use /bioentity/<type>/<id> endpoint when type is function.

Also, the response given by the bioentity/function/<id> route is different than /bioentity/<type>/<id> route.

This is because we don't do marshaling of the response in bioentity/function/<id>

deepakunni3 commented 5 years ago

This requires,

refactoring /bioentity/function/<id> such that its returning the proper marshaled association results
calling /bioentity/function/<id> implementation when type in /bioentity/<type>/<id> is function, to ensure consistency

This is a bigger discussion that involves @lpalbou and @cmungall