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

Deal with non-i18ned attribute values #58

Merged
merged 2 commits into from
Nov 20, 2024
Merged

Conversation

vuilleumierc
Copy link
Member

  1. Deal with non-i18ned attribute values

Optional i18ned attributes such as 'title' and 'internationalTitle' are in fact not mutually exclusive. GeoServer goes as far as setting 'title' to the first of the i18n values on PUT request if 'title' is not specified but 'internationalTitle' is.
Here we set precedence on the i18n attribute if it is present in the GET response payload and we force a null value on the non-i18ned attribute in the PUT payload to avoid unwanted side effects.

  1. Add delete feature type method

Closes #57

Optional i18ned attributes such as 'title' and 'internationalTitle' are in fact not mutually exclusive. GeoServer goes as far as setting 'title' to the first of the i18n values on PUT request if 'title' is not specified but 'internationalTitle' is.
Here we set precedence on the i18n attribute if it is present in the GET response payload and we force a null value on the non-i18ned attribute in the PUT payload to avoid unwanted side effects.
@vuilleumierc vuilleumierc merged commit 9bfbf4f into master Nov 20, 2024
1 check passed
@vuilleumierc vuilleumierc deleted the put-i18n-title branch November 20, 2024 15:32
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.

Handle default value of i18n attribute on PUT
2 participants