You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provide new interface to implement a PSProvider #5789
The current apis are difficult to use which spawned middle-ware like SHiPS and Simplex. The downside to these additional layers is performance impact. Consider having new apis that simplify the PSProvider authoring experience.
Who can design the API? I am afraid that the design and implementation may take several months to work intensively. We have to start now if we want to get this to 6.1.0.
Ilya (@iSazonov) at this time, I don't have any engineers available to design nor implement this. If you're interested, feel free to tackle this and author an RFC. Later this month I'm going to re-triage the issues marked for 6.1.0-Consider and will probably move a bunch to 6.2.0-Consider.
WG-Engine discussed this one a bit today. Our general consensus is that this is a huge scope of work and currently not well-defined. Accomplishing this would likely involve a lengthy RFC process and a full rewrite of the provider spec / a completely new provider specification before we ever got to looking at any implementations. Reviewing it also would be a lengthy task.
Given that, our opinion is essentially that this is unlikely to happen until funding and support is provided from the PowerShell team, and that means this kind of issue is pretty much unilaterally in Steve Lee (@SteveL-MSFT)'s (and/or other PowerShell PMs') ballpark as to if and when it might get worked on, much less completed.
The addition of a major-investment Github label was briefly suggested, as a shortlist of things that are nice to dream about but basically only the pwsh PMs can realistically move forward in the project. This might be one such issue. 😁
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented on Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
Activity
iSazonov commentedon Jan 4, 2018
Who can design the API? I am afraid that the design and implementation may take several months to work intensively. We have to start now if we want to get this to 6.1.0.
SteveL-MSFT commentedon Jan 4, 2018
Ilya (@iSazonov) at this time, I don't have any engineers available to design nor implement this. If you're interested, feel free to tackle this and author an RFC. Later this month I'm going to re-triage the issues marked for
6.1.0-Considerand will probably move a bunch to6.2.0-Consider.iSazonov commentedon Jan 4, 2018
Oh, I don't know this code so well to redesign it. I know a few weaknesses and will continue to investigate this code.
It would also be good to have PowerShell Core roadmap on next 1-2 years so that the community can work effectively with MSFT.
SteveL-MSFT commentedon Jan 4, 2018
Ilya (@iSazonov) excellent point about an updated roadmap. Will work on it and target getting it published by GA time.
jzabroski commentedon May 1, 2019
The ideal design pattern for "provider model" (in my opinion) is that of "implicit traits" (Scala) or type classes (Haskell).
vexx32 commentedon Mar 6, 2023
WG-Engine discussed this one a bit today. Our general consensus is that this is a huge scope of work and currently not well-defined. Accomplishing this would likely involve a lengthy RFC process and a full rewrite of the provider spec / a completely new provider specification before we ever got to looking at any implementations. Reviewing it also would be a lengthy task.
Given that, our opinion is essentially that this is unlikely to happen until funding and support is provided from the PowerShell team, and that means this kind of issue is pretty much unilaterally in Steve Lee (@SteveL-MSFT)'s (and/or other PowerShell PMs') ballpark as to if and when it might get worked on, much less completed.
The addition of a
major-investmentGithub label was briefly suggested, as a shortlist of things that are nice to dream about but basically only the pwsh PMs can realistically move forward in the project. This might be one such issue. 😁microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.