Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-9872

Enhance workflow editor autocompletion

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • Enhance workflow editor autocompletion
    • False
    • None
    • False
    • To Do
    • 100% To Do, 0% In Progress, 0% Done
    • ---
    • ---

      During the POC phase, only the Scaffolder actions and JIRA OpenAPI specs have been incorporated in the editor to enable function autocompletion.

      The editor itself is already prepared and fetching specs from the backend through `getSpecs` (see plugins/orchestrator/src/api/api.ts) but the backend is hardcoding only those two aforementioned specs (see listStoredSpecs in plugins/orchestrator-backend/src/service/WorkflowService.ts).

      This is heavily dependent on the default repository we are using to load workflows and other assets (see https://github.com/tiagodolphine/backstage-orchestrator-workflows/tree/main/workflows/specs)

      As users would be allowed to load multiple repositories in https://issues.redhat.com/browse/KOGITO-9873, we should create a generic mechanism that discovers all available specs and returns them to the front end.

       

            Unassigned Unassigned
            gcaponet Guilherme Caponetto
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: