alphagov / alphagov/locations-api
Its hard to identify Large User Postcodes
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 8
- Forks
- 2
- Avg merge
- 6h 38m
- Merged PRs (30d)
- 19
Description
We should really have a rake task which can give you the basic information on a postcode, because otherwise it's hard to identify when a problem is down to a postcode being an LUP (which can't be used for local_transaction or find-your-council lookups, but can be used for Places Manager lookups or geocoding).
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 examining the repository's existing Rake tasks and the postcode lookup entry points named in the issue. Define the task's basic postcode output so it makes Large User Postcodes identifiable and distinguishes support for local_transaction, find-your-council, Places Manager, and geocoding lookups. Done means the task can provide that information for a supplied postcode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100