Description

The GeoServer GSIP 234 - Advertise and Enforce Attribute Restrictions will introduce two type of restrictions rules for attributes:

• range supported by numerical attributes with minimum and maximum configurations
• options supported by numerical and string attributes represented as a list of available options

This task should include following improvements:

• Detect and parse of range and options restrictions from WFS DescribeFeatureType response
• Add validation logic to detect features with invalid properties and highlight them in the table with information tooltip. Validation logic should be based on the restrictions and nillable value
• Inform users about invalid attribute with a tooltip and a red dot over the save button
• Attributes with options restrictions should show only the list of available values
• Inform user about the possibility that a field could be a primary key and it does not need editing even if it's highlighted. We are not getting this information from the backend so we should include a configurable list of attribute names that could be considered primary keys (e.g. fid, ogc_fid)

What kind of improvement you want to add? (check one with "x", remove the others)

• Minor changes to existing features

Other useful information