cyclestreets / cyclestreets/cyclescape
Library item types need to be same as standard message types
Open
Nobody has claimed this yet.
library
- Dominant language
- PLpgSQL
- Stars
- 34
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
The library items should basically have the same structure as existing messages, and therefore have a greater range of types.
The absence of a link type is particularly keenly-felt. Putting a link within an unstructured block of text is not really sufficient.
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
No files, tests, or entry points are named. Start by locating how standard messages and library items define their types, then determine the scope needed for library items to support the same range, including links. Done means the two structures and supported item types are aligned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100