fix: make sure a fallback layer id is rendered in time in order to support sorting #588
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an additional
requestUpdate()
after the initialpropertyCheck()
, to force the DOM to re-render. The reason for this is that SortableJS needs the layerid
present in order to work correctly.The
requestUpdate()
is only called in case it is needed, e.g. if theid
ortitle
were changed by thepropertyCheck()
.Fixes #584.