cloudfoundry / cloudfoundry/stratos
Remove hard link between cf and autoscaler packages
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Cf package depends on autoscaler in two places
- ApplicationsModule (brings in app autoscaler tab via CfAutoscalerModule)
- this also creates a depency in CloudFoundryTestingModule
- CardCfInfoComponent (shows AS version via fetchAutoscalerInfo)
Ideally it would be nice to remove this hard link and only show functionality if autoscaler package is present
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the dependencies from ApplicationsModule and CardCfInfoComponent through CfAutoscalerModule and fetchAutoscalerInfo, including the CloudFoundryTestingModule dependency. Determine how the CF package can operate without the autoscaler package; done means the hard links are removed and autoscaler functionality appears only when that package is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100