Skip to content

Port rules provider fix to release-2.3 #16051

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.

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

Merged
merged 3 commits into from
May 24, 2017

Conversation

jramsay
Copy link
Member

@jramsay jramsay commented May 23, 2017

Add all rules to the RulesProvider’s RulesMap regardless of user options
Pass FormatCodeSettings to the FormattingContext
Update RuleOperationContext's InContext to check if a rule should be applied based on the FormattingCodeOptions
Update rules to consume new RuleOperationContext options check
compareDataObjects fix to check if the object has the same number of keys
Fixes:
• TS: [TSServer] Formatting RulesProvider (re)initialization performance issues
• VS: Bug 373219: [TypeScript Perf] WebForms_DDRIT.0300.Typing HTML5 HTML regressed Duration_AccumulatedElapsedTime (60ms)

@jramsay jramsay requested a review from mhegazy May 23, 2017 23:11
@jramsay jramsay requested review from minestarks and billti May 23, 2017 23:12
@jramsay jramsay changed the title Port rules provider fix to release 2.3 Port rules provider fix to release-2.3 May 23, 2017
Copy link
Member

@minestarks minestarks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

didn't review the specifics

@jramsay jramsay merged commit 196aba6 into release-2.3 May 24, 2017
@mhegazy mhegazy added this to the TypeScript 2.3.4 milestone May 25, 2017
@mhegazy mhegazy deleted the PortRulesProviderFixToRelease-2.3 branch November 2, 2017 21:04
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants