Skip to content
This repository was archived by the owner on Oct 11, 2022. It is now read-only.

Conversation

@brianlovin
Copy link
Contributor

@brianlovin brianlovin commented May 31, 2018

Status

  • WIP
  • Ready for review
  • Needs testing

Deploy after merge (delete what needn't be deployed)

  • hyperion (frontend)

brianlovin and others added 30 commits May 4, 2018 16:00
As @brianlovin noticed in #3199, the CD for the desktop app wasn't
working because CircleCI only runs builds for commits that are
associated with a PR.

While we could set CircleCI to run builds for all branches, that's a
very suboptimal solution as it would run a ton of unnecessary builds.

I came to wondering, why does the CD for alpha work if it doesn't build
branches? Hidden in the CircleCI docs I found this snippet:

> Note: For your default branch, we will always build all commits.

Which explains why alpha CD works, but production CD doesn't.

This patch is a very simple solution to this problem: we run desktop CD
on the alpha branch. That is fine because the desktop CD only creates a
draft GitHub release and we have to manually publish that release for
anybody to get the update, so it doesn't matter if we CD from alpha or
production!
Instead of relying on a bunch of custom behavior this patch makes it so
we use the standard `autoUpdater.checkForUpdatesAndNotify()` method and
call it every 15 minutes.

It also adds a menu item called "Check for updates" so users can
manually check for updates.
Dont show deleted threads in notifications dropdown
The desktop app requests the same paths as the browser would, which
means previously it would also get the server-side rendered HTML.

The problem is that the server-side rendered frontend doesn't know that
it's being rendered for the desktop app, and thusly renders the standard
frontend, which looks crappy in the desktop app.

This patch disables server-side rendering enterily when a req from the
desktop app comes in, which fixes that issue.
Fix focussing body when pressing enter in title in composer
Update banning-users.md to include mutations to disable feature flags…
@spectrum-bot
Copy link

spectrum-bot bot commented May 31, 2018

Warnings
⚠️

These modified files do not have Flow enabled:

  • config-overrides.js

Generated by 🚫 dangerJS

@brianlovin brianlovin merged commit 1f70fa1 into production May 31, 2018
@brianlovin brianlovin deleted the 2.4.3 branch May 31, 2018 21:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants