Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

elsa-designer-tree TypeError: activityDescriptor.inputProperties is not iterable

See original GitHub issue

Project Context

Hello 👋! The company I work for is adding a workflow feature to our platform to let our users more easily connect our various products and I’m trying to get a rough proof of concept up with Elsa.

I’ve have the @elsa-workflows/elsa-workflows-studio@2.0.1 installed from NPM and am consuming the package from a react application. Currently, I have the elsa-studio-root component embedded just to get things up and running.

The Problem

The component loads fine initially, but nothing happens when I try to add a new activity (repro: open activity modal from workflow definition screen and try to select an activity). The console has the following error

TypeError: activityDescriptor.inputProperties is not iterable

which is being thrown from here.

It seems like the ActivityDescriptor type that the javascript is expecting doesn’t match the type that the API is returning

It’s weird though because I can’t repro when starting the API + Dashboard using docker

Issue Analytics

State:
Created 2 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

josephdangerstewartcommented, Jul 6, 2021

About the type error, make sure you include <script src="/build/assets/js/monaco-editor/min/vs/loader.js"></script> on your page (make sure the path is correct too)

This worked, thanks for your help!

Regarding workflow definitions per group, this would require a customized UI, so you will probably want to build your own dashboard app (using react) and communicate with your own backend API to manage workflow definitions.

We decided to end up using this approach! On top of the permission stuff, there are some semantic differences between how we’re thinking of workflows and how Elsa thinks about workflows. There’s also a lot of UI that we’ll need that’s specific to our domain for which we have existing react libraries we could leverage. I do think the Elsa dashboard is really nice though, keep up the awesome work!

0reactions

sfmskywalkercommented, Jul 1, 2021

PS. I’m closing this issue since the original issue seems to have been resolved, but feel free to continue the conversation here, or separately in a different issue or discussion thread if you want to explore a specific topic further.