Replies: 6 comments 3 replies
-
can confirm that even the verbatim example for "Emit" also does not pass the front-end JSON validation that was just committed, so perhaps there is presently some issue with my syntax vs. what the server needs to see?
Validation:
|
Beta Was this translation helpful? Give feedback.
-
Does it work if you skip the emit:
event:
type: ....
source: .... It looks like the example you are using is invalid 😞 When in doubt, check the |
Beta Was this translation helpful? Give feedback.
-
Yeah I tried earlier without the "with" (and various other permutations) it would accept it before, but now that the schema is validating on the client it won't accept the version without "with" - but before it would accept the version above, and "appear to" run... And yes, I have been consulting the DSL + DSL Reference files extensively throughout (I don't want to waste others' bandwidth when I can debug things on my own - but I do have my limits being brand new to this spec + framework!) Enjoy your time away! (I am travelling as well, but working a little while I go) |
Beta Was this translation helpful? Give feedback.
-
...and another limitation is that I've never really worked in C# or dotnet :) However I do work very extensively in fullstack JS/TS + JSON schema, so hopefully I can be at least a little bit useful :) Based on your suggestion, this morning now I've validated the example against the spec JSON Schema I checked both with and without the "with" (with an external validator tool that I use regularly) and both appear to be valid. However the front-end of synapse there are (now) various errors with the different permutations (one example below) Additionally it shows this validation error in red at bottom (among many other things Yet if I play with moving source/type around, no combination really seems to solve it for the parsing that synapse wants to see?... But again, prior to the front-end validation commit, different versions were "accepted" via the UI. And "runs" were completed without errors... however the other workflow with the "on" handler (see original pair above) did not automatically create and run a new instance, so the external POST side-effect didn't occur unless I manually triggered that 2nd workflow. I have no idea if there is a system issue or if i'm feeding configs in in wrong. And ... along the lines of your CLI suggestion, what would be ideal for me is if I could create a script and populate a folder of workflows an ingest them programmatically at startup -- because IF synapse works for me it will involve tight coupling with a very configuration-oriented "host" system that's built entirely in JS/TS - and synapse (or eventually a TS implementation of the spec) would be the "router" that makes different things happen at the right times. I know there is SOME way to inject these config files this if I code it all myself, but just thought I'd ask if there's already something like a "startup workflows folder" kind of config option? Thanks again - and no rush on replies here! |
Beta Was this translation helpful? Give feedback.
-
That's wierd indeed, I'll check what's happening. It might be a bug introduced by the latest front end validation PR.
Oh, I think I get it now! So far, events published by
That can be easily achieved, I'd be happy to add that feature! |
Beta Was this translation helpful? Give feedback.
-
Amazing thank you so much Charles And yes that makes sense about the event bus stuff - part of why I asked here in the first place was that I wasn't sure if what I was trying/testing was even "supposed to" work but then when I tried things and saw the "correlator" stuff jump to life I got excited and was like 🤔 maybe it does have an "internal" event bus. I'll give that sink config stuff a go! And also thanks for the tip on the swagger docs/endpoint - that might be more practical for now (and will also make it more obvious to me what kinds of integrations I'd be able to layer in myself) |
Beta Was this translation helpful? Give feedback.
-
I have two test workflows, designed for me to test + understand Synapse's internal event handling:
My issue is that I the 2nd one (below) doesn't trigger POST to webhook.site -- EXCEPT if I manually create a
post-order-from-event
instance (which isn't how this is supposed to work, right?). Is my syntax wrong (I tried as JSON too so I know it is valid in a "mechanical" sense)... Or do I have the wrong idea about what is supposed to happen with "schedule -> on" ? I read all the docs I could find and that's what I think it's supposed to do...Beta Was this translation helpful? Give feedback.
All reactions