FlowFuse / FlowFuse/flowfuse

npm run generate:types created different output depending on developers flowfuse.local.yml

Open Beginner friendly
#7,734 0 comments 0 reactions 0 assignees View on GitHub
needs-triage
Dominant language
JavaScript
Stars
400
Forks
89
Avg merge
1d 20h
Merged PRs (30d)
149

Description

### Current Behavior

Local config (e.g. license and other settings) changes what is enabled for a the running instance of the forge app.

### Expected Behavior

A single default config is loaded by the `scripts/dump-`openapi.js ` not the one on the default search path.

This needs to have all optional API endpoints enabled and a valid enterprise license.

### Steps To Reproduce

Run `npm run generate:types` when you have a none default config file

### Environment

- FlowFuse version:
- Node.js version:
- npm version:
- Platform/OS:
- Browser:

### Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

Contributor guide

Open the contributing guide

Research direction

Start with scripts/dump-openapi.js and run npm run generate:types using a non-default local config. Trace which configuration the generator loads and compare the generated output with and without flowfuse.local.yml. Done means the command consistently uses one default config with optional API endpoints enabled and a valid enterprise license.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
api, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.