Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit the number of bufferable features #715

Merged
merged 3 commits into from
Mar 18, 2022

Conversation

theduckylittle
Copy link
Member

The browser can only handle so much, limit the number of
features GeoMoose willingly buffers from the results.

refs: #711

@klassenjs
Copy link
Member

Is there a clean way we could tell the user why the buffer button is disabled?

@theduckylittle
Copy link
Member Author

Could put a message on the bottom. Would need to translate that message to our various languages 😬

@klassenjs
Copy link
Member

klassenjs commented Mar 18, 2022

Think it is worth it or just merge it? As is it could just look broke without saying what could fix it. Although that is still better than crashing. Other than that, the PR does what it says on the tin.

The browser can only handle so much, limit the number of
features GeoMoose willingly buffers from the results.

refs: geomoose#711
@elil
Copy link
Member

elil commented Mar 18, 2022 via email

@theduckylittle
Copy link
Member Author

Yeah... I'm sympathetic to giving the user too much information. I've updated this to show a modal when there are too many features.

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.

3 participants