microsoft / microsoft/PowerShell-FeatureFlags
Migrate code to C# or F#
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 24
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
The PowerShell code works, but at this point it might be better to implement the cmdlet in pure C#.
This should buy us some more advantages, as the dotnet tool seems to not support very well the PowerShell sources, treating them more as resources than as source files, and requiring us to write ad-hoc scripts to do the "build" and publishing of the code.
This would also remove the ugly part of the code where we try to find the JSON and JSON Schema DLLs and load assemblies directly from those files.
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 reviewing the existing PowerShell cmdlet and the ad-hoc scripts used for its dotnet build and publishing workflow. Compare a C# or F# implementation against the current assembly-loading approach; done means the cmdlet is migrated and the stated source-handling and JSON assembly-loading problems are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, fsharp, powershell
- Domain
- build-system, cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100