-
Notifications
You must be signed in to change notification settings - Fork 11
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
Show the ad for the mobile app to everyone not on an android #2203
Conversation
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.
fine!
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 like the revised approach, just a question affecting the readability of one of your functions here
@@ -103,7 +103,7 @@ defmodule DotCom.Mixfile do | |||
{:jason, "1.4.4", override: true}, | |||
{:logster, "1.1.1"}, | |||
{:mail, "0.3.1"}, | |||
{:mbta_metro, "0.0.49"}, | |||
{:mbta_metro, "0.0.50"}, |
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.
Was upgrading metro necessary as part of this PR?
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.
No, but we might as well.
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 won't block approval on this, but in general I don't like lumping library upgrades together with unrelated features. It runs the risk of creating hard-to-revert surprises, especially when the library is in alpha, as metro is.
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.
- https://github.com/mbta/dotcom/pull/2203/files#r1817198719 <-- I think we need to suppress the banner on ferry pages too, per the A/C's of the ticket.
- I also think that the logic in
mobile-app-banner.js
is getting complicated enough, especially with all the regexes, that it would be worth adding tests. This can be a follow-up, but unless that logic gets a lot simpler (for instance, I don't really understand why we're not just showing it on every page), I'd hesitate to iterate on it anymore without tests.
https://app.asana.com/0/555089885850811/1208568379309256/f
I didn't put it on the schedule finder because it is a modal, not a page. It is on the schedule page below the schedule finder.