PSCommunity Call Questions for May 16, 2019 about powershell-rfc

[SteveL-MSFT]

@vexx32 it will be published along with preview.1 which is expected this week

[fMichaleczek]

a short status/direction around the meta issue would be welcome
PowerShell/PowerShell#3240 (Fix Various PowerShell Class Issues)

[iSazonov]

Is there a specific list of fixes/improvements you are most concerned about?

In last days we discussed that we need unify -Path/-LiteralPath somehow because we have tons of fixes in the area and no end in sight.
The same must be done for Cultures/CaseSensitive/Ordinal (discussion about Select-String and etc. cmdlets)
A long time ago we made unification for Encoding and it works well for a long time. So we have positive experience for unification and should continue.

These two observations are related to performance issues. There are many places where we could improve it but we did little.

Another question that worries me is how will we keep the code clean after MSFT team silently removed CodeFactor, which not only actually saved us from formatting discussions but also led us to remove almost all formatting problems (in last time most of commits was without style issues! Now there is only problems with the documentation that should be corrected gradually I believe).

We still are waiting vNext HelpSystem (decoupled and Markdown supported).

It would be great to start implementing a new formatting system (ala PSMore)

It also worries me that we started to add coloring (and Markdown rendering) to the main code, although it had to be isolated with the formatting system and ConHost.

[vexx32]

@SteveL-MSFT if anyone was taking minutes for the call, might be a good idea to leave a link to those here for the purposes of folks finding their way here later and saving them a good bit of time figuring out which call exactly it was in 6 months time. 🙂

[SteveL-MSFT]

@joeyaiello generally published the notes and transcript here, we should just add a link to this discussion issue as well

[fMichaleczek]

@SteveL-MSFT wrong month ?

[vexx32]

Plans for possibly incorporating some long-needed fixes / improvements in PS7? There's quite a few issues that are an an impasse due to the whole deal with breaking changes. With a new major version that encompasses (almost?) all of the missing WinPS features, seems like the best possible time to break some eggs to make a great omelette 😉

Also in that vein; plans post PS7 initial release? New features planned on the horizon? General direction of development? I'm all for community driven development, and I've seen a lot of great ideas and features from the community that look like great fun, but id love to see a roadmap of what you guys are planning to have done as well!

[SteveL-MSFT]

@fMichaleczek fixed!

[SteveL-MSFT]

@vexx32 roadmap will be covered on the call. Is there a specific list of fixes/improvements you are most concerned about? Some may already be on the roadmap

[adrian-andersson]

I'd like an update to Module Manifests to include exporting of ENUMS, CLASSES etc

[vexx32]

I think @iSazonov covers a lot of what I was going to mention, @SteveL-MSFT. Those are all things that I think we should look to get done or well on the way to getting done by PS7. You might want to add reference links for those issues so the team can easily review the discussion for the community call, as well. 😄

The other ones I'd like to bring up are (we may not have time to discuss all of them, so feel free to gloss over anything you consider particularly unimportant, but... hey PS7 is on the horizon so)

• PowerShell/PowerShell#8819 (@Jaykul's Cmdlet-keyword suggestion)
• PowerShell/PowerShell#8357 (Where-Object improvements)
• PowerShell/PowerShell#7983 (Write-Progress / ProgressPreference)
• PowerShell/PowerShell#7851 (Paging improvements)
• PowerShell/PowerShell#7930 (Select-Object -First X)
• PowerShell/PowerShell#7835 (duck-typing / ValidateProperty)
• PowerShell/PowerShell#7506 (param names for .NET methods)
• PowerShell/PowerShell#7124 (comment)
• PowerShell/PowerShell#2337 (here-string syntax)
• PowerShell/PowerShell#3240 (null-conditionals)

[Tr4pSec]

Any thoughts on a screen/tmux like feature for powershell?

[Jaykul]

Regarding Terminals (and the new Console) ...
PowerShell's Host.PrivateData and Host.UI.RawUI. colors need to be RGB

In the console we can now have default "background" and "foreground" colors which are not indexes into the base16 colors, and there's no way to get PowerShell to respect them.

[SteveL-MSFT]

Closing this as we discussed this in the Community Call

[iSazonov]

When will it be published?

[vexx32]

@SteveL-MSFT quick ping post-long-weekend -- y'all mentioned the roadmap briefly on the call, is that published anywhere yet, or are you guys still working on it? 🙂