alisha-1000 commented on issue #534:
URL: https://github.com/apache/wayang/issues/534#issuecomment-3929016421
Thanks for reporting this ,
It sounds like the JSON API currently logs the exception to the server
terminal but does not propagate a structured error response back to the client
when an invalid Wayang plan is submitted. This can make debugging difficult for
API consumers.
Ideally, the endpoint should:
Catch plan parsing / validation exceptions
Return a proper HTTP status code (e.g., 400 Bad Request for invalid plans,
500 for internal errors)
Provide a structured JSON error response (e.g., { "error": "...", "details":
"..." })
Avoid exposing internal stack traces unless running in debug mode
This would make the API more robust and production-ready.
If you’d like, I can look into adding proper exception handling around the
endpoint and implementing consistent error responses.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
