Uploaded image for project: 'Fuse Tooling'
  1. Fuse Tooling
  2. FUSETOOLS-2560

Provide warning validation when a component is the same than an existing component definition id from the catalog

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 10.1.0
    • None
    • None

      to be discussed
      is it worthy?
      We will miss all the cases of components are not in the catalog.
      Why a user should care about a component definition that he/she is not using?

      Should we validate only for component definition used in the same route, same context?

              Unassigned Unassigned
              apupier@redhat.com Aurélien Pupier
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: