make the error handling less awkward #10

New Issue

Closed

opened 2024-05-11 17:21:02 +00:00 by Yessiest · 0 comments

Yessiest commented 2024-05-11 17:21:02 +00:00

Owner

Copy Link

currently the handle method only allows to define headers and contents of the page sent. it does not allow setting a different code (which is occasionally useful), and since all errors are caught at the top level of the call stack (usually in a path's process_wrapped method), setting up a pipeline to catch errors on a lower level is almost entirely useless, as the error is handled immediately and then sent to the response finalizer.

currently the handle method only allows to define headers and contents of the page sent. it does not allow setting a different code (which is occasionally useful), and since all errors are caught at the top level of the call stack (usually in a path's process_wrapped method), setting up a pipeline to catch errors on a lower level is almost entirely useless, as the error is handled immediately and then sent to the response finalizer.

Yessiest closed this issue 2024-05-11 20:43:06 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

Labels

Clear labels   

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

wontfix

This won't be fixed

No Label

bug

duplicate

enhancement

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: Yessiest/landline#10

No description provided.