Skip to content
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

Bump jscodeshift from 0.5.1 to 0.11.0 in /webrtc/tools #3

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Mar 16, 2021

Bumps jscodeshift from 0.5.1 to 0.11.0.

Release notes

Sourced from jscodeshift's releases.

v0.7.0

Added

Changed

  • Moved from BSD to MIT license

Fixed

v0.6.4

Changed

  • Allow writing tests in TypeScript (#308)
  • Better handling of .gitingore files: Ignore comments and support \r\n line breaks (#306)

v0.6.3

Fixed

  • Don't throw an error when jscodeshift processes an empty set of files (#295, @​skovhus).
  • renameTo should not rename class properties (#296, @​henryqdineen).
  • Custom/unknown CLI parameters are parsed as JSON, just like nomnom used to do.

v0.6.2

Changed

  • @babel/register/@babel/preset-env is configured to not transpile any language features that the running Node process supports. That means if you use features in your transform code supported by the Node version you are running, they will be left as is. Most of ES2015 is actually supported since Node v6.
  • Do not transpile object rest/spread in transform code if supported by running Node version.

Fixed

  • Presets and plugins passed to @babel/register are now properly named and loaded.

v0.6.1

Added

  • Tranform files can be written in Typescript. If the file extension of the transform file is .ts or .tsx, @babel/preset-typescript is used to convert them. This requires the --babel option to be set (which it is by default). ( #287 , @​brieb )

Changed

  • The preset and plugins for converting the transform file itself via babeljs have been updated to work with babel v7. This included removing babel-preset-es2015 and babel-preset-stage-1 in favor of @babel/preset-env. Only @babel/proposal-class-properties and @babel/proposal-object-rest-spread are enabled as experimental features. If

... (truncated)

Changelog

Sourced from jscodeshift's changelog.

[0.11.0] 2020-09-01

Changed

  • Updated recast to latest

[0.10.0] 2020-06-01

Changed

  • Updated flow-parser to latest, and enabled Flow Enums parsing by default when using Flow parser

[0.8.0] 2020-05-03

Changed

  • Dropped support for Node versions 6 and 8

[0.7.0] 2019-12-11

Added

Changed

  • Moved from BSD to MIT license

Fixed

[0.6.4] 2019-04-30

Changed

[0.6.3] 2019-01-18

Fixed

  • Don't throw an error when jscodeshift processes an empty set of files (#295, @​skovhus).
  • renameTo should not rename class properties (#296, @​henryqdineen).
  • Custom/unknown CLI parameters are parsed as JSON, just like nomnom used to do.

[0.6.2] 2018-12-05

Changed

  • @babel/register/@babel/preset-env is configured to not transpile any language features that the running Node process supports. That means if you use features in your transform code supported by the Node version you are running, they will be left as is. Most of ES2015 is actually supported since Node v6.
  • Do not transpile object rest/spread in transform code if supported by running Node version.

Fixed

  • Presets and plugins passed to @babel/register are now properly named and loaded.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by flowtype, a new releaser for jscodeshift since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Mar 16, 2021
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Apr 26, 2021

Superseded by #17.

@dependabot dependabot bot closed this Apr 26, 2021
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/webrtc/tools/jscodeshift-0.11.0 branch April 26, 2021 07:51
mrego pushed a commit that referenced this pull request Nov 22, 2021
…eVisibilityKeeper::PrepareToSplitBlockElement()` before splitting a text node

It does the following things when caret is collapsed in a text node in a `<p>`
or `<div>` element.

1. Split the text node containing caret to insert `<br>` element
2. Insert `<br>` element after it
3. Split ancestor elements which inclusive descendants of the `<p>` or `<div>`
4. Delete the `<br>` element if unnecessary from the left paragraph

#3 and #4 are performed by `HTMLEditor::SplitParagraph()` and it calls
`WhiteSpaceVisibilityKeeper::PrepareToSplitBlockElement()` correctly before
splitting the block.  However, in the case (caret is at middle of a text node),
the text has already been split to 2 nodes because of #1.  Therefore, it fails
to handle to keep the white-space visibility.

So that I believe that the root cause of this bug is, the method does much
complicated things which are required, and doing the redundant things will
eat memory space due to undo transactions.  However, for now, I'd like to fix
this with a simple patch which just call the preparation method before splitting
the text node because I'd like to uplift this if it'd be approved (Note that
this is not a recent regression, the root cause was created by bug 92686 which
was fixed in 17 years ago:
<https://searchfox.org/mozilla-central/commit/2e66280faef73e9be218e00758d4eb738395ac83>,
but must be annoying bug for users who see this frequently).

The new WPTs are pass in Chrome.

Differential Revision: https://phabricator.services.mozilla.com/D130950

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1740416
gecko-commit: 73567f6c2bcfa078836a36760498bb11747561dd
gecko-reviewers: m_kato, smaug
mrego pushed a commit that referenced this pull request Apr 26, 2024
…attempt #3

This converts IDL-exposed promises in ReadableStream,
ReadableStreamBYOBReader, ReadableStreamDefaultReader, and
ReadableStreamGenericReader to use typed ScriptPromiseResolver
instead of StreamPromiseResolver and to return typed
ScriptPromises.

Bug: 329702363
Change-Id: I8ad1af1a7c9c909d711881ce7621c6c9fac58931
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5429731
Reviewed-by: Adam Rice <[email protected]>
Reviewed-by: Nidhi Jaju <[email protected]>
Commit-Queue: Nate Chapin <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1289397}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
0 participants