Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-24897

Config endpoints does not show user resolver constraints on schema such as dublincore

    XMLWordPrintable

    Details

      Description

      Since NXP-23256 and this commit, https://nightly.nuxeo.com/nuxeo/api/v1/config/schemas/dublincore?fetch.schema=fields does not show the userResolver constraint on dc:creator, dc:lastContributors etc.

      It shows:

              "creator": {
                  "constraints": [
                      {
                          "entity-type": "validation_constraint", 
                          "name": "string", 
                          "parameters": {}
                      }
                  ], 
                  "type": "string"
              }
      

      while coverage for instance is fine

              "coverage": {
                  "constraints": [
                      {
                          "entity-type": "validation_constraint", 
                          "name": "string", 
                          "parameters": {}
                      }, 
                      {
                          "entity-type": "validation_constraint", 
                          "name": "directoryResolver", 
                          "parameters": {
                              "directory": "l10ncoverage"
                          }
                      }
                  ], 
                  "type": "string"
              }
      

      This is wrong, the config endpoint purpose was actually to make available this kind of information.

      On the server side, constraints are called during validation. We disabled creator, lastContributor and contributors validation because they are system metadata filled by Nuxeo. This was about to avoid Directory request on a field known to be valid.

      We want to know the constraints on a field even if the validation is disabled. We can add a new field on resolver (validation), in order to disable the validation but allow to serialise constraints in config endpoint.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 1 hour
                  1d 1h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.