-
Notifications
You must be signed in to change notification settings - Fork 32
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
Merge upstream v8.2.11 #78
Conversation
It appears that one of the dependencies of [email protected] (not specifically listed in `package.json`) causes an out-of-memory crash, though it is not yet clear which one. However, due to the way NPM resolves package versions, it is not sufficient to merely pin the version of `cssnano` itself, as NPM may still pull in newer versions of the dependencies. The correct fix would be to identify the problematic cssnano dependency and add the package with a version constraint to `package.json`. Since the package has not yet been identified, though, instead this commit merely relies on package-lock.json to avoid pulling in the problematic package. The package-lock.json from this commit was created by the following steps: 1. Reverting package-lock.json to its version prior to the commit that merges in changes from upstream v8.2.11. 2. Modifying package.json to pin cssnano to 5.0.17 rather than 5.1.0. 3. Running `npm install` to make the minimal updates to the old `package-lock.json` to satisfy the new contents of `package.json`. Note that deleting `package-lock.json` and then recreating it by running `npm install` will NOT work; it will pull in the problematic cssnano dependency.
…nx-immaterial into merge-upstream-v8.2.11
@@ -106,6 +106,14 @@ export function watchSearchQuery( | |||
history.replaceState({}, "", `${url}`) | |||
}) | |||
|
|||
/* Set query from parameter */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This now makes the assignment to el.value
and call to el.focus
above redundant, so we can remove that.
@@ -106,14 +106,6 @@ export function watchSearchQuery( | |||
history.replaceState({}, "", `${url}`) | |||
}) | |||
|
|||
/* Set query from parameter */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is fine to keep it, and instead do the removal I mentioned, as that will minimize merge conflicts in the future.
As far as the redundant assignment to
(Unfortunately github does not allow you to comment on unmodified lines very easily) That should be changed to just:
|
@@ -110,7 +110,6 @@ export function watchSearchQuery( | |||
param$.subscribe(value => { // TODO: not ideal - find a better way | |||
if (value) { | |||
el.value = value | |||
el.focus() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is better to keep the call to el.focus()
here and instead remove it from a few lines above in the same file. That way we minimize merge conflicts.
This whole review system is all messed up for some reason. I can't even do a simple reply unless I'm looking at the PR diff. And then that seems to look like a separate review comment... |
Thanks. Just one last change: 8274da5#diff-36117e5373aef262c0fc3e0d37c56bec5d51de771f9d91a7100aa5def753dfb8L90 that line should remove the assignment to |
oops, I didn't notice that missing bit in the snippet you posted. |
This looks ready to merge, thanks! |
merge in updates from upstream v8.2.11
closes #55
There were 3 files that had conflicts:
src/assets/javascripts/components/search/query/index.ts
Merged in this PR.
src/assets/javascripts/components/search/result/index.ts
Ignored these changes
tools/build/index.ts
Merged only single line changes and import statements - ignored block changes at bottom