-
Notifications
You must be signed in to change notification settings - Fork 132
Todo List: Separate Cloud Foundry code from the core modules. #3675
Comments
|
Move any cf related effects from |
Move any cf related reducers from |
Move any cf related selectors from |
We have two |
|
Work out what to do with the metrics code, this is used across the cloudfoundry and kubernetes (in the SUSE repo) code. Do we need a metrics plugin? How would the other plugins access the actions, components etc. of another plugin? |
Check where else we use QParam. |
|
Now covered in #3789
|
Endpoint health checks should come from endpoint configuration. Should check all registered endpoint types for one. |
Ensure |
Move entity relations & validation into cf module |
Ensure nothing that can be lazy loaded is imported in CloudFoundryPackageModule (vs CloudFoundryModule) |
Move cf effects into cf module
|
Ensure there's no references to CFAppState in non-cf areas (favoriteEntitiesSelector, favoriteGroupsStateSelector, internalEventStateSelector, etc) |
Things to check from store folder: grep -R "/cloud-foundry/" * |
This ticket should act as a todo list of areas of the core frontend code that references Cloud Foundry.
We're doing this as part of the extensions work and to improve code maintainability and testability.
Note: This list is not exhaustive and should not replace a deliberate look through the codebase.
The text was updated successfully, but these errors were encountered: