You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a reason why updateServiceSettings converts workspace names to lowercase, while others methods seem to accept camelcased name ?
Is this a general rule in geoserver to have lowercased workspace names ? I do this for pg tables to avoid case issues, but I was not aware of this in geoserver.
Beside, the api seems to accept character such as @ for names, which is nice, while such characters make the UI unresponsive. This could be reported in GeoServer repo, but maybe you can enlighten me on that issue.
Geosapi version : 0.4-0
Geoserver version : 2.14.1
R version 3.5.2
Thanks !
F
The text was updated successfully, but these errors were encountered:
Hi,
Is there a reason why
updateServiceSettings
converts workspace names to lowercase, while others methods seem to accept camelcased name ?Is this a general rule in geoserver to have lowercased workspace names ? I do this for pg tables to avoid case issues, but I was not aware of this in geoserver.
Beside, the api seems to accept character such as
@
for names, which is nice, while such characters make the UI unresponsive. This could be reported in GeoServer repo, but maybe you can enlighten me on that issue.Geosapi version : 0.4-0
Geoserver version : 2.14.1
R version 3.5.2
Thanks !
F
The text was updated successfully, but these errors were encountered: