* Prepare-Release.ps1: Make dateTime.ToString("MM/dd/yyyy") to work on exotic set-ups
On my machine, I experimented with the registry, and the worst part is that I don't remember/know how to reset it back.
The work items that script produces, do have datetimes for the upcoming releases in the `MM-dd-yyyy` format, and then I have to correct them by hand.
`dateTime.ToString("MM/dd/yyyy")` does produce the date in the format of `MM-dd-yyyy` on my machine. This also happens if I write a corresponding .NET app.
The fix that I am proposing makes it work on my specific setup and hopefully breaks no one else. I understand if you are hesitant to take it. Let me know, I'll see how I can restore my setting.
But on the other hand, I don't think it makes anything worse, it only makes things more robust, so maybe take it?
* Use [CultureInfo]::InvarialtCulture
Switch on StarExpr's operand, avoiding a panic on unhandled types.
Include the expression in the type name for SelectorExpr.
Include the * for StarExpr in type declarations.
* [js-api-parser] Don't add members as types
This PR uses the id of the token to determine whether it should be added as a
member or a type.
* bump js-api-parser version to 1.0.8
* Fix role assignment for user auth
* PR fb
* Apply suggestions from code review
Co-authored-by: Heath Stewart <heaths@outlook.com>
---------
Co-authored-by: Heath Stewart <heaths@outlook.com>
* Correct the name of JS package folder
* Uncomment the package verification
* Logging more info for troubleshooting
* Get sdkType and directory from the package info
* Read and forward upstream response stream in chunks whenever possible to avoid buffering
---------
Co-authored-by: Mike Harder <mharder@microsoft.com>
* assume by default the tspconfig is a url
* check if config file exists in local file system
* remove unused fetch function
* get tspconfig.yaml through git to account for private repo links
* changelog
* use Telemetry Client Via DI
* Condition automaticRevision in AutoReviewController to prevent Exception
* Avoid null error in Review Page due to ReviewContent.APIRevisionsGrouped
* update APIView Error Page
* Add SnapSHot Debugger to allow debugging of Live site
* Add ConflictedFile to git-helpers.ps1, add git-helpers.tests.ps1 to exercise basic functionality.
* Add `resolve-asset-conflict.ps1` a script that can autoresolve an assets.json file.
---------
Co-authored-by: Scott Beddall (from Dev Box) <scbedd@microsoft.com>
Co-authored-by: Scott Beddall <45376673+scbedd@users.noreply.github.com>
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
catalinaperalta
Chidozie Ononiwu
Peng Jiahui
Daniel Jurek
Liudmila Molkova
Wes Haggard
Anton Kolesnyk
Joel Hendrix
Scott Beddall
Heath Stewart
Rodge Fu
Ray Chen
Travis Prescott
Jeremy Meng
JoshLove-msft
Christopher Scott
Jose Arriaga Maldonado
Matt Ellis
Harsha Nalluru
Ben Broderick Phillips
Libba Lawrence
Jesse Squire