Flask: disposition.Notify handler should maybe forward?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Instead of just rendering the notification directly, it should stash the notification message somewhere and then forward to a new URL that renders the stashed message. This is possibly a more general solution for part of issue #18.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Flask disposition.Notify handler and read issue #18 for the broader context. Trace how the notification is currently rendered, then determine where the message could be stashed and how a new URL would render it. Done means the handler forwards instead of rendering directly and the stashed notification is displayed at the new URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100