max-mapper / max-mapper/hexbin
Additional meta-fields?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 530
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
A couple ideas for potentially useful new meta-fields:
- `repo_url` (or similar): A number of PRs I've reviewed include a link to the repository or website in the `online_order_url` field. Others embed that in the description field. Would it make sense to include a place for that as it's own field?
- `type`: One other interesting bit of information that feels missing is some way to group stickers that represent similar things (e.g., events, organizations, software packages, etc.). For example, hex stickers are especially popular in the R community, as branding for packages. I could envision a predefined list to help keep things manageable.
If you're open, I could take a shot at this. One question would be whether it makes sense to define different types for different programming languages. My inclination is yes, although that might get unwieldy...
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
Review how online_order_url and description currently store repository or website links. Consider the proposed repo_url and type meta-fields, including the question of language-specific types; done requires an agreed metadata design and clearly defined field behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100