kestra-io
Plural errors in the flow are chained without any separator making it difficult to decipher.
Hi @satvik2131 ! Already better indeed, could be good to test the display with errors (as long as possible, you may increase the id length if the task I.E, to test the wrapping) and in the same time with warnings.
Also, could be more readable for long errors to separate them, something like that :
Top notch addition could be to have a scroll bar i guess, but let's wait before trying to implement it.
@ReLoutre , if we implement this separation then individual scrollbar in every error would appear ,would that be fine , also the error string comes as one , so need to do some string manupulation , I have enable scrollbar in the whole error box . Let me know which approach to go with ?
https://github.com/user-attachments/assets/40509712-3199-46de-a123-5f08506ffdfb
When referring to scroll bar i was thinking of a vertical one, to navigate through all the errors. What's more, i think we should use wrapping of words to avoid having super long lines.
I can work on the vertical scrolling part and wrapping as well but for wrapping of words I need some guidance how we wanted to process it : like creating a regex to text function or using custom messages instead of these regex patterns . Please mention the approach to go further and will start working on it .
Would be best to not reinvent the wheel here, and use the current word wrapping technique already used in the application (like Logs, Search, YAML Editor, No Code Editor, etc.)
