Skip to content
This repository has been archived by the owner on Jun 18, 2019. It is now read-only.

Visual update (again) #24

Merged
merged 28 commits into from
Jun 9, 2017
Merged

Visual update (again) #24

merged 28 commits into from
Jun 9, 2017

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented Jun 9, 2017

Pulls in the changes originally presented via #17 in the visual-update branch. Something went wrong with the merge of #16 and #17 together, i.e. visual-update -> updated-rusty-secrets -> master. The problem was surely caused by my manual resolution of conflicts.

Noticed in #23 that we're not seeing the visual updates that we should be, and @garrettr pointed out that went awry with the merge.

In creating this branch, I re-merged visual-update into master and confirmed that the new assets display properly. All tests are passing locally on Mac. The Linux builds still create incomplete packages (#20), but incorporating changes from #22 in a disposable branch showed green lights across the board. Specifically (since we don't have CI), the testing story looks like:

Mac:

  • npm run test passes
  • npm run test-e2e passes
  • npm run dist succeeds
  • ✅ manually installed built package behaves well

Linux:

  • npm run test passes
  • npm run test-e2e fails (expected; we use a headless environment in linux for now)
  • npm run dist succeeds
  • ⚠️ deb package shows blank screen (but Linux builds broken #20 resolves!)

So it looks like if we merge this and also #22, we're back in business. Tagging @GabeIsman for re-review of the changes, in case I screwed up any of the conflict resolution.

Closes #23.

GabeIsman and others added 28 commits December 3, 2016 13:16
Rather than storing the state. This is much better since with this
approach removing the mismatched share correctly updates everything
that shares are now matched.
This is an unfortunate consequence of the current two-package.json
setup that used to be required by electron-builder. Apparently recent
versions are much smarter and do not require this setup. Would be great
to get away from and merge our two package.jsons to avoid this and
other complications.
Remerging the 'visual-update' branch due to errors in original merge in
PR #17. These must have been related to reconciliation of changes
between #16 and #17 by yours truly.
@conorsch conorsch requested a review from GabeIsman June 9, 2017 00:37
@conorsch conorsch mentioned this pull request Jun 9, 2017
Copy link
Contributor

@GabeIsman GabeIsman left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for figuring this out. I don't envy the careful work it must have taken.

@conorsch
Copy link
Contributor Author

conorsch commented Jun 9, 2017

😘 😎 :shipit:

@conorsch conorsch merged commit f88cbda into master Jun 9, 2017
conorsch pushed a commit that referenced this pull request Jun 9, 2017
The `icns2png` command was referencing the old path to the `app.icns`
file, which is no longer valid as of #17 and #24. Fixing that command
allows the icns -> png format conversion work as intended. No changes
required to `package.json`, since the paths there are already correct.

Closes #23.

Signed-off-by: Conor Schaefer <conor@freedom.press>
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.

App still uses default Electron icon
2 participants