Skip to content

Ambiguity for user to differentiate between user side error and system internal error. #1244

@Yash2004Codes

Description

@Yash2004Codes

Description :
The application currently swallows unexpected system errors across multiple core services (parser.service.ts,editor.service.tsx, etc.). When an internal exception occurs (e.g., parser crash, storage failure, conversion error), the error is caught but not surfaced to the user. The UI shows a generic "Invalid document" state, leading to Bad user experience as Diagnostic Pannel shows no errors (means there is no error from user input) but preview pannel shows error.

How to Reproduce
1)Open apps/studio/src/services/parser.service.ts (or editor.service.tsx).
2) Modify a method having try-catch block to manually throw error : by copying throw new Error("Simulated System Crash"); on very first line in try block
Image
3) Open studio website and refresh
4) Observe that no Error Toast, Modal, or specific Alert appears. The user receives no feedback that the Invalid Document Error message is from Internal System Error and not from user side.
Image

Expected behavior
Expected a small toast message at UI conveying user that error is from internal system.

Fix :
Adding a toast message inside src/services/parser.service.ts , src/services/editor.service.tsx , src/services/converter.service.ts, src/services/format.service.ts

Once this issue is approved ,I would be happy to fix this and open a PR ! Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions