8000 Suggestion: Provide a type accelerator for [System.Management.Automation.SemanticVersion] · Issue #3460 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]
Skip to content

Suggestion: Provide a type accelerator for [System.Management.Automation.SemanticVersion] #3460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
mklement0 opened this issue Mar 30, 2017 · 8 comments
Closed

Suggestion: Provide a type accelerator for [System.Management.Automation.SemanticVersion] #3460

mklement0 opened this issue Mar 30, 2017 · 8 comments
Labels
Issue-Enhancement the issue is more of a feature request than a bug Resolution-Fixed The issue is fixed. Up-for-Grabs Up-for-grabs issues are not high priorities, and may be opportunities for external contributors WG-Language parser, language semantics
Milestone
6.1.0-Consider

Comments

@mklement0
Copy link
Contributor
mklement0 commented Mar 30, 2017 •
edited
Loading

Now that semantic version numbers (semver) are becoming ubiquitous, it would be nice to be able to do something like

$ [semver] '1.2.3-preview-02+build42'

Major Minor Patch Label         
----- ----- ----- -----         
    1     2     3 preview-02+build42

instead of what you currently need to do:

$ [System.Management.Automation.SemanticVersion] '1.2.3-preview-02+build42'
@iSazonov iSazonov added WG-Language parser, language semantics Issue-Enhancement the issue is more of a feature request than a bug labels Mar 30, 2017
@SteveL-MSFT SteveL-MSFT added the Up-for-Grabs Up-for-grabs issues are not high priorities, and may be opportunities for external contributors label Mar 30, 2017
@SteveL-MSFT SteveL-MSFT added this to the 6.1.0 milestone Mar 30, 2017
@oising
Copy link
Contributor
oising commented May 31, 2017

Ok, this looks mindlessly simple. Can I take this?

@mklement0
Copy link
Contributor Author

@oising: I can't speak for the team, but I think it's fine to just go ahead, now that you've announced your intent. Thanks for taking it on.

@SteveL-MSFT
Copy link
Member

@oising consider it yours! I can only assign to formal team members so don't worry about that

@oising
Copy link
Contributor
oising commented Jun 28, 2017

Just a quick update - I got busy, and then got lost trying to get everything to build in VS2017 - but I'm back on track.

@oising
Copy link
Contributor
oising commented Jun 28, 2017

I don't see anything wrong with allowing [semver] in constrained language mode, so I'm permitting it there. If there's anything outlandish about this, bring it up in the PR review I guess.

@oising oising mentioned this issue Jun 29, 2017
Merged
@iSazonov
Copy link
Collaborator

@oising Can we close the Issue as fxed?

@oising
Copy link
Contributor
oising commented Jul 12, 2017

Yes :) My first (and hopefully not last) PR.

@iSazonov
Copy link
Collaborator

@oising Good start!

@iSazonov iSazonov added the Resolution-Fixed The issue is fixed. label Jul 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Enhancement the issue is more of a feature request than a bug Resolution-Fixed The issue is fixed. Up-for-Grabs Up-for-grabs issues are not high priorities, and may be opportunities for external contributors WG-Language parser, language semantics
Projects
None yet
Milestone
6.1.0-Consider
Development

No branches or pull requests
4 participants
@mklement0 @oising @SteveL-MSFT @iSazonov
0