Increase flexibility for maximum windows limit

[ishikabhoyar]

Is your feature request related to a problem? Please describe.
Currently, the application enforces a hardcoded maximum window limit of 50 for Electron environments and 15 for web environments. This can be limiting for users who need more flexibility, especially those working with multiple APIs or power users with capable hardware. There's no way for users to adjust these limits based on their needs or system resources.

Describe the solution you'd like
I would like the maximum window limit to be configurable through the application's settings or configuration file. Sensible defaults can remain (e.g., 50 for Electron, 15 for web), but users should be able to override these values based on their workflow and hardware capabilities. Ideally, the settings dialog should have a UI control for this value, and the limit should be validated to prevent unreasonable usage.

Describe alternatives you've considered

• Keeping the current hardcoded limits (less flexible, not ideal for all users)
• Having only environment-based defaults without user override

Additional context
The current implementation is found in packages/altair-core/src/config/index.ts in the Altair GraphQL repository:

max_windows = isElectron ? 50 : 15;

Providing a configurable option will improve user experience and allow power users to optimize their workflow.

[imolorhe]

Are you hitting the limit?!! How?! 😅

[imolorhe]

No issues adding this though. Sounds reasonable. I just never thought this limit would be an issue.

[imolorhe]

I'd like to learn more about your use case though and your feedback on the tool, as it seems you're a power user.

[ishikabhoyar]

Hi @imolorhe ,
I'd like to take up this feature request and submit a PR for it. From looking at the codebase, specifically packages/altair-core/src/config/index.ts, I can see that implementing a configurable window limit would involve:

1. Adding a new setting in the application's configuration system
2. Updating the UI to expose this setting to users (perhaps in the Settings dialog)
3. Modifying the window creation logic to respect the user-configured limit

I'm thinking of implementing it with reasonable defaults (keeping the current 50/15 values) but allowing users to override them through settings. Would you prefer any specific validation constraints on the maximum value users can set? Also, would you want this persisted between sessions?

I'll aim to have a PR ready as one of my good first issue, if this approach sounds good to you.

[imolorhe]

@ishikabhoyar sounds good. You'll want this stored in the settings and it will automatically be preserved along with other settings

[ishikabhoyar]

Thanks, @imolorhe !

Perfect, I’ll proceed with adding the new setting to the configuration system and exposing it in the Settings dialog. I’ll also make sure it gets persisted alongside the existing settings so users don’t lose their preferences between sessions.

For validation, I’ll keep the sensible defaults (50 for Electron, 15 for web), but add a reasonable upper cap (e.g., maybe 70 for Electron and 30 for web) to prevent extreme values from causing performance issues. Does that sound like a good balance to you, or would you prefer the limits to be completely open-ended?

I’ll start working on this and aim to submit a PR soon.

[imolorhe]

@ishikabhoyar let me know if you're still looking into this, otherwise happy to pick it up myself

[ishikabhoyar]

yea im working on it. will update shortly.