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

Feature type customization can prevent correct <featurecaption> serialization #55

Open
prushforth opened this issue Dec 7, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@prushforth
Copy link
Member

prushforth commented Dec 7, 2022

The new feature type customization in GeoServer 2.21 allows flexible attribute output renaming, but if the renamed attribute contains a space, it results in default <featurecaption> of "Feature" even if a feature caption string has been appropriately set.

For example, if you rename the STATE_NAME attribute to "State Name" for output features:

image

and then you set the <featurecaption> string to contain a property placeholder that should serialize the renamed attribute:

image

it results in the default "Feature" string being used:
image

@prushforth prushforth added the bug Something isn't working label Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant