Data services that implement *Data interfaces should include the appropriate test functions in their specs.
These go over all methods in the interface & check that they're "wired up" correctly.
See e.g. the change in ExternalSourceDataService for an issue that is easy to miss but was highlighted by these new tests
Override linkPath/responseMsToLive/constructIdEndpoint
- in class body for inheritable classes (for clarity: it's the first thing you'd read, variable name is right there)
- in constructor for composable classes
* wrapped services must be 'synchronized' with their wrapper
* moved these overrides up in the argument list for emphasis (implementing a new composable feature? first thing is to use the same endpoint!)
Data services should extend BaseDataService (or IdentifiableDataService) for low-level functionality and optionally wrap "data service feature" classes for
- create
- findAll
- patch / update
- put
- delete
