linksplatform / linksplatform/Data.Doublets
Define the Each behaviour we Null (0) or default value is passed as restrictions
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Now if the 0 passed as source the behaviour is confusing (looks like it was undefined).
https://github.com/Konard/Currency/blob/AdditionImplementation/Currency/DB/DataBaseScripts.cs#L115
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 DataBaseScripts.cs around line 115 in the linked branch and trace how Each handles null, 0, and default restriction values. Use the issue image and current behavior to determine the intended distinction; done means those cases have an explicitly defined, non-confusing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100