Open dglazer opened 5 years ago
For the sake of unit and integration testing with the schema, it might be nice to include reference/mock client and server (plus tests) in this repo — changes to the spec that mess up client or server functionality could be caught with CI.
If we do pull this code out, should we come up with some convention for repo names (e.g., ga4gh-drs-service
, ga4gh-drs-api
, ga4gh-drs-reference
, etc.)?
We want to separate the schema (which is the purpose of this repo) from mock clients/servers and test code. This issue tracks deleting the no-longer-used infrastructure.