cyclestreets / cyclestreets/cyclescape
Expose the consultation end and target decision dates for planning applications
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 34
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
When determining whether to look into a planning application further, the consultation end date and target decision dates. For example if they have passed there's likely no point in looking further. Could also automatically add a date item to the thread created so that it appears in the deadline list.
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 planning-application data and the thread deadline-list handling. Confirm where consultation end and target decision dates are stored or exposed, then define how those dates should appear and whether a thread date item is created; completion should make both dates available for planning and show the intended deadline entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100