microsoft / microsoft/json-document-transforms
Any reason not to support NET 6/8
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 115
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Any reason not to add NET 6/8 support to the library, also any indication about how complete the library is wrt the specification
Contributor guide
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
The issue names .NET 6/8 support and asks about completeness against the specification, but mentions no files, tests, or entry points. Start by locating the library's target-framework configuration and existing specification coverage; done means support is assessed or added with the remaining gaps clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100