It would be very helpful to see the call stack when debugging Microflows. For example, if I have a Microflow that is used for logging exceptions and I have a process that might call it 4 different times I can’t tell which of those calls resulted in the logging Microflow being called until I step out of the Microflow.
+1
I have the issue, that an entity is commited somehow, but I don't know who's triggering this. How can I tell when I do not have a stacktrace?
Again. Mendix lacks some really fundamental stuff. I'm annoyed.
Yes, this would be very helpful. A good start would be to have a call stack debuggin pannel that shows a callstack as a list of subsequential executed microflows / nanoflows that are clickable to open them in the moddeller.
Now, since Mendix doesn't compile to code it might be difficult to get the variables for that particular piece of the stack but it would already be very helpful just to see the microflows nanoflows stack in a table. Similar to the data is currently available in the Java API.
waiting for this for 2 years now :(
+1
+1
+1
+1
Recognizable to all (former) high code developers… ;)
Standard in most IDE’s. Hope to see it soon in Mendix Studio Pro too.