linksplatform / linksplatform/Data
Make ILinks more generic (support string and other types)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The link address can be represented using any type.
There should be IUnsignedNumber constraint removed.
To do it, we might also introduce ILinksConstants, to be able to abstract away constants to be anything (like string and so on).
It is needed at https://github.com/link-foundation/link-cli.
We also might add IUnsignedLinks (as inherited from ILinks and IUnsignedNumber) with IUnsignedNumber constraint for backward compatibility.
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 ILinks and IUnsignedNumber in the Platform.Data library, then trace how link addresses and constants are constrained. Review whether ILinksConstants and a backward-compatible IUnsignedLinks are needed, using the link-cli requirement as context. Done means link addresses can use types such as string while existing unsigned-number usage remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100