Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ServerlessWorkflow Parser to return a comprenhensive list of errors #3733

Closed
fjtirado opened this issue Oct 16, 2024 · 0 comments · Fixed by #3756
Closed

ServerlessWorkflow Parser to return a comprenhensive list of errors #3733

fjtirado opened this issue Oct 16, 2024 · 0 comments · Fixed by #3756
Assignees

Comments

@fjtirado
Copy link
Contributor

fjtirado commented Oct 16, 2024

Description

The existing serverless workflow parser is designed to fail as soon as possible to not waste resources.
So, when an error is found the parser is aborted.
That means that if a workflow contain several errors, only the first one is reported.
Thats not good in some situations where iteration of changes is costly, like IA generators.
Therefore, we should modify the parser to collect as much errors as possible without changing the overall design.

Implementation ideas

No response

@fjtirado fjtirado self-assigned this Oct 16, 2024
fjtirado added a commit to fjtirado/kogito-runtimes that referenced this issue Oct 29, 2024
fjtirado added a commit to fjtirado/kogito-runtimes that referenced this issue Oct 30, 2024
fjtirado added a commit to fjtirado/kogito-runtimes that referenced this issue Oct 30, 2024
fjtirado added a commit that referenced this issue Oct 31, 2024
* [Fix #3733] Collecting more than one error message

* [Fix #3733] Including process validation check

* [Fix #3733] Adding transition check
rgdoliveira pushed a commit to rgdoliveira/kogito-runtimes that referenced this issue Nov 7, 2024
* [Fix apache#3733] Collecting more than one error message

* [Fix apache#3733] Including process validation check

* [Fix apache#3733] Adding transition check
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant