database of secondary nodes and primary nodes
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
It would be useful to have an easy to access hash table `secondary node => primary node` for each package. I do this for LearnM2 (e.g. see [here](https://github.com/mahrud/LearnM2/blob/96534a8e20bb227cdae6f94cdb8ac86ca662914e/_packages/v1.25.11/Elimination.json#L2-L13)) to postpone link generation to the client side, but this would also resolve the problems in #1643 (or more specifically #786)
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 reading the linked LearnM2 Elimination.json example and the discussions in #1643 and #786. Then locate where package data and link generation are produced in M2. Done means each package exposes an easy-to-access secondary-node-to-primary-node mapping that supports client-side link generation and addresses the referenced issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100