Skip to content

fix: allow to save a remote data with unloaded data #2657

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

Merged
merged 1 commit into from
Apr 23, 2025

Conversation

yohanboniface
Copy link
Member

When loading remote data fails, the layer is in state "unloaded", and thus it was not possible to save it.
This "isLoaded" check is made for non remote layer so that we don't save it by mistake with no data.

Also, let's allow to edit non loaded layers, this check was there when settings was not on db, so not all loaded at map init, again not to override with incomplete metadata.

When loading remote data fails, the layer is in state "unloaded",
and thus it was not possible to save it.
This "isLoaded" check is made for non remote layer so that we don't
save it by mistake with no data.

Also, let's allow to edit non loaded layers, this check was there
when settings was not on db, so not all loaded at map init, again
not to override with incomplete metadata.
@yohanboniface yohanboniface merged commit 92ca581 into master Apr 23, 2025
5 of 6 checks passed
@yohanboniface yohanboniface deleted the save-remote-unloaded branch April 23, 2025 15:49
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