Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-11537

Support required field metadata in data shapes

    XMLWordPrintable

Details

    • % %
    • ?
    • 0
    • 0% 0%

    Description

      (Migrated from https://github.com/syndesisio/syndesis/issues/2397)

      Author: Zoran Regvart
      Assignees: unassigned

      This is a...

      [!-- Check ONLY one of the following options with "x" --]
      [pre][code]
      [x] Feature request
      [ ] Regression (a behavior that used to work and stopped working in a new release)
      [ ] Bug report [!-- Please search GitHub for a similar issue or PR before submitting --]
      [ ] Documentation issue or request
      [/code][/pre]

      The problem

      [!--
      Briefly describe the issue you are experiencing (or the feature you want to see implemented on Syndesis).
      + For BUGS, tell us what you were trying to do and what happened instead.
      + For NEW FEATURES, describe the User Persona demanding it and its use case.
      --]
      Currently we don't take into account any metadata of a field in the data shape. Both JSON Schema and XML Stylesheet provide support for setting if property is required, allowed range of the property and similar metadata.
      Supporting this would help the user performing the mapping to know what mappings must be performed (required fields), and we could perform mapping validation based on that metadata.

      Requires atlasmap/atlasmap#90 atlasmap/atlasmap#50

      Expected behavior

      [!-- Describe what the desired behavior would be, enlistin gthe acceptance criteria. --]
      Help the user by highlighting what fields are required and need values mapped to them.

      Attachments

        Activity

          People

            Unassigned Unassigned
            zregvart@redhat.com Zoran Regvart
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: