Skip to content

Conversation

@firewave
Copy link
Collaborator

No description provided.

@firewave firewave changed the title some Settings::premium usage cleanups some Settings::premium related cleanups Jan 12, 2026
@sonarqubecloud
Copy link

@danmar
Copy link
Owner

danmar commented Jan 12, 2026

Just a wild idea.. I think it would be nice if --premium.. options could be moved out and read from the premiumaddon.json file (regular addoninfo format). That could allow better integration of other addons also for instance namingng .

I have no concrete plans for how to specify options.

@firewave
Copy link
Collaborator Author

Just a wild idea.. I think it would be nice if --premium.. options could be moved out and read from the premiumaddon.json file (regular addoninfo format). That could allow better integration of other addons also for instance namingng .

I have no concrete plans for how to specify options.

That is exactly my goal.

The rough idea is to collect the addons and then collect option like --<addon>= (or similar) and then pass them to the addon. How the latter is supposed to be work needs to be worked out.

To add those options to --help the addon would either support that option as or have a entry which specifies those (or both) which will be put into the AddonInfo. Same with --errorlist.

Will file a ticket on this in the next few days.

@firewave firewave merged commit db22e09 into danmar:main Jan 13, 2026
72 of 73 checks passed
@firewave firewave deleted the premium-x branch January 13, 2026 01:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants