Upgrade prettier to version 1.15.3 #40
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ prettier (1.15.2 → 1.15.3) · Repo · Changelog
Release Notes
1.15.3
🔗 Changelog
Commits
See the full diff on Github. The new version differs by 43 commits:
Release 1.15.3fix(typescript): do not throw errors on bigint keyword (#5577)feat(angular): support interpolation in attributes (#5573)fix(api): normalize file path for `getFileInfo` (#5570)feat(html): update angular-html-parser (#5565)test: update snapshotsfix(vue): group slot-scope correctly (#5563)Updating cosmiconfig to not cache .js config files when told not to (#5558)fix(vue): tweak semicolon for single expression in event bindings (#5519)Improve union types with leading comments (#5575)chore(build): es5 compatibility for browser (#5560)fix(html): correct column for error code frame (#5553)feat(typescript): support BigInt (#5546)fix(typescript): do not change `module` into `namespace` and break/hug their body correctly (#5551)fix: update editorconfig-to-prettier (#5550)fix(ng,vue): do not normalize attribute names (#5549)test: improve snapshots (#5521)feat(angular): do not print colon for ngIf (#5542)fix(html-in-js): do not add quotes for interpolation-only attributes (#5544)fix(javascript): add missing parens for binary in optionalMember (#5543)feat(yaml): preserve the first document head end marker (#5502)fix(javascript): upgrade @babel/parser to 7.1.6 (#5530)ensure --list-different + --write reports status code 0 (#5512)fix(html): do not touch comments (#5525)fix(html): do not add extra indent for js template in script (#5527)fix(vue,ng): do not normalize tag names (#5526)fix(vue): preserve custom block (#5458)feat(javascript): enable logical assignment (#5489)chore: tweak azure-pipelines.yml (#5498)Replace Appveyor badge with Azure Pipelines badge (#5492)fix(markdown): do not trim content in inline-math (#5485)chore(deps): update `postcss-scss` (#5481)feat(html): support ie conditional start/end comment (#5470)fix(html): leading space for leading interpolation in textarea is sensitive (#5468)fix(html): preserve content for element in `<pre>` correctly (#5473)fix(markdown): add more category to CJK regex (#5480)fix(typescript): do not add invalid semi for construct in interface with prettier-ignore (#5469)Delete Appveyor config (ref #5410)Fix tests for Windows and add Azure Pipelines for cross platform CI (#5410)fix(typescript): inline method decorators should stay inlined (#5444)Add more information on how to configure ALE (#5454)Add HTML to the list of supported language in the docs (#5427)Bump Prettier dependency to 1.15.2Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands