#10699: Attribute table crash when additional geometries in attributes#11266
Merged
offtherailz merged 1 commit intogeosolutions-it:masterfrom Jul 3, 2025
Merged
#10699: Attribute table crash when additional geometries in attributes#11266offtherailz merged 1 commit intogeosolutions-it:masterfrom
offtherailz merged 1 commit intogeosolutions-it:masterfrom
Conversation
…es in attributes - fix the crash app issue due to multi geometry fields by editing 'isGeometryType' util and 'describeFeatureTypeToAttributes' util - add unit tests
1 task
offtherailz
approved these changes
Jul 3, 2025
Member
offtherailz
left a comment
There was a problem hiding this comment.
It works for me. No crashes anymore.
Member
|
@ElenaGallo, could you please test this on DEV ? By opening the feature grid, dev (and I think also QA, when imported) was crashing. After this fix it works. |
Contributor
|
Test passed, @mahmoudadel54 please backport to 2025.01.xx. Thanks |
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this pull request
Jul 11, 2025
…etries in attributes (geosolutions-it#11266)
Contributor
Author
Backport is done --> #11307 |
tdipisa
pushed a commit
that referenced
this pull request
Jul 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR includes: fixing the crash app issue due to multi geometry fields by
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#10699
What is the new behavior?
The new bahavior is if there are some multi geometry fields in layer data and user wants to explore attribute table data --> the geometry field will be the first one on fetched fields and other geometry ones will be ignored
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information