In the v2 API, if a method found an unrecognized , the id was put in a special list, which was returned as a special result.
In the v3 API, you get a 400 error if any id is invalid.
We should probably have a way to recover the v2 behavior or something equivalent to it using either an option to all methods that take ids as arguments, or as a separate validation method. The latter is cleaner and more orthogonal, but would be a pain for users and for performance.
I think there is a separate issue somewhere about having propinquity give explanations of why a taxonomy node failed to make it into the synthetic tree; that should be coordinated with this more general question, which has to do with OTT ids that were deprecated long ago, or mistyped.
This will come to a head when we discontinue the v2 API, because this is one thing you can do with the v2 API that you can't easily do with the v3 API. (In v3, to find out what the unrecognized ids were, you have to parse the error message, because neo4j doesn't let us return json error responses.
Revert to something similar to v2 behavior, adding extra fields to result
Same as 1. but only when enabled when requested by a flag parameter
Define a new method specifically for validating ids. Return value would be list(s) of invalid ids. Client would call that first, then use it to filter the id list for a subsequent mrca or induced subtree call
In the v2 API, if a method found an unrecognized , the id was put in a special list, which was returned as a special result. In the v3 API, you get a 400 error if any id is invalid. We should probably have a way to recover the v2 behavior or something equivalent to it using either an option to all methods that take ids as arguments, or as a separate validation method. The latter is cleaner and more orthogonal, but would be a pain for users and for performance.
I think there is a separate issue somewhere about having propinquity give explanations of why a taxonomy node failed to make it into the synthetic tree; that should be coordinated with this more general question, which has to do with OTT ids that were deprecated long ago, or mistyped.
This will come to a head when we discontinue the v2 API, because this is one thing you can do with the v2 API that you can't easily do with the v3 API. (In v3, to find out what the unrecognized ids were, you have to parse the error message, because neo4j doesn't let us return json error responses.