Conversation
Briefly describe future plans for MDS-Core
|
| Work-in-progress. These are Lacuna priorities; feedback from other MDS-Core contributors is welcome. | ||
|
|
||
| * Improved documentation for MDS-Core operation | ||
| * Multi-MDS-version support (MDS 1.0 and later) |
There was a problem hiding this comment.
Thanks for sharing! After our meeting we discussed this internally and wondered, if you plan this two-way, or if you are only thinking about the agency api?
Here is an example: Would GET /policies with an Accept header for Version 1.0 actually return the policy in 1.0, even if the mds-core repo has already adapted MDS 1.2 (assuming there are any differences in a policy 1.0 vs. 1.2)?
| * Passenger Services deployment for LADOT (MDS 2.0 alpha) | ||
| * Add support for new modes architecture (MDS 2.0 final) | ||
| * Increased test coverage | ||
| * Support non-AWS cloud providers |
| * Add support for Policy Requirements (MDS 1.2) | ||
| * Passenger Services deployment for LADOT (MDS 2.0 alpha) | ||
| * Add support for new modes architecture (MDS 2.0 final) | ||
| * Increased test coverage |
There was a problem hiding this comment.
Are there particular packages you have in mind as lacking in test coverage right now? I think most of the service packages in mds-core are all right. Is there a global maximum of line coverage we should be shooting for? I've been on a team once where we went for 95% which struck me as a tad excessive, but 80 feels pretty good.
4 participants
Briefly describe future plans for MDS-Core