You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In version 0.x, is it possible to limit quality checking and unit tests to only part of the application?
We could then aim for highest quality in the OpenCDMS generic components – and have more flexibility/rapid development with the Climsoft-specific components.
To help achieve this – would it make sense for the Climsoft-specific components be separated physically, e.g. into a subdirectory, or even into a separate package?
Current OpenCDMS generic components:
Login screen
Dashboard
User profile
Settings (for all users)
Current Climsoft-specific components:
Climsoft Metadata management
Climsoft Data entry forms
Over time, we can replace Climsoft-specific components (which use the Climsoft API) with OpenCDMS generic components that work with multiple CDMSs (using the new OpenCDMS API that will be developed over the next 6-12 months).
The text was updated successfully, but these errors were encountered:
In version 0.x, is it possible to limit quality checking and unit tests to only part of the application?
We could then aim for highest quality in the OpenCDMS generic components – and have more flexibility/rapid development with the Climsoft-specific components.
To help achieve this – would it make sense for the Climsoft-specific components be separated physically, e.g. into a subdirectory, or even into a separate package?
Current OpenCDMS generic components:
Current Climsoft-specific components:
Over time, we can replace Climsoft-specific components (which use the Climsoft API) with OpenCDMS generic components that work with multiple CDMSs (using the new OpenCDMS API that will be developed over the next 6-12 months).
The text was updated successfully, but these errors were encountered: