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

Add Errors namespace to the Website #200

Closed
ricardozanini opened this issue May 31, 2024 · 2 comments · Fixed by #221
Closed

Add Errors namespace to the Website #200

ricardozanini opened this issue May 31, 2024 · 2 comments · Fixed by #221
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@ricardozanini
Copy link
Member

ricardozanini commented May 31, 2024

What would you like to be added:
We have errors namespaced by our domain in the new DSL: https://github.com/serverlessworkflow/specification/blob/main/dsl-reference.md#standard-error-types

It would be nice to have them documented (dynamically, by using CI) on the website as well.

Why is this needed:
Users can fetch the error-rich description by accessing the URL when seeing the log in a runtime implementation

@ricardozanini ricardozanini added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels May 31, 2024
@ricardozanini ricardozanini self-assigned this May 31, 2024
@JBBianchi
Copy link
Member

Do you want me to take care of it @ricardozanini ?

@ricardozanini
Copy link
Member Author

@JBBianchi oh please! The idea is to have a JSON, TXT, and HTML representation. But for a first iteration, I believe just TXT makes sense now.

JBBianchi added a commit to neuroglia-io/serverlessworkflow.github.io that referenced this issue Jan 10, 2025
- Added dynamic routes to support specification errors
Notes:
- Return type based on Accept header
- Enabled SSR on netlify

Closes serverlessworkflow#200

Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants