Consider restructuring request lifecycle callbacks
Open
Nobody has claimed this yet.
Lift5
- Dominant language
- Scala
- Stars
- 1.3k
- Forks
- 275
- PR merge metrics
- No merged PRs in 30d
Description
Mailing List thread: https://groups.google.com/d/msg/liftweb/oVp-FfWbWmw/9bguLNPiAQAJ
Lift has a variety of lifecycle callbacks around the beginning of requests, sessions, and co. They're also scattered in a few different places. Consider how we can rework these to be easier to understand, discover, and work with.
Contributor guide
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 with the linked mailing-list thread, then inventory Lift’s request and session lifecycle callbacks and where they are currently defined. The issue names no files or tests; completion would require an agreed restructuring that makes these callbacks easier to understand, discover, and use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100