equinor / equinor/fusion-framework
app: fetch config via configUrl from manifest instead of provider.getAppConfig
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 10
- Avg merge
- 19h 40m
- Merged PRs (30d)
- 150
Description
In `packages/modules/app/src/app/flows.ts`, `handleFetchConfig` has a TODO suggesting it should use the `configUrl` directly from the manifest rather than going through `provider.getAppConfig(appKey, version)`:
```ts
// TODO - use the configUrl directly from the manifest
// fetch config from provider
const subject = from(provider.getAppConfig(payload.appKey, payload.build?.version)).pipe(
```
Contributor guide
Research direction
Start in packages/modules/app/src/app/flows.ts at handleFetchConfig and trace how the manifest and its configUrl are available alongside the current provider.getAppConfig call. Done means the flow fetches configuration from the manifest's configUrl instead of provider.getAppConfig(appKey, version), while preserving the surrounding config-fetch behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100