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

Don't error on invalid platform for search #708

Closed
eviljeff opened this issue May 1, 2018 · 11 comments
Closed

Don't error on invalid platform for search #708

eviljeff opened this issue May 1, 2018 · 11 comments
Labels
state:stale Issues marked as stale. These can be re-opened should there be plans to fix them.

Comments

@eviljeff
Copy link
Member

eviljeff commented May 1, 2018

From https://bugzilla.mozilla.org/show_bug.cgi?id=1457707

A search such as https://addons.mozilla.org/en-US/firefox/search/?q=blah&platform=OpenFoo&appver=59.0.2 gives an error on new frontend because the API rejects "OpenFoo" as an invalid platform; on the legacy frontend the invalid platform is silently ignored and it falls back to All Platforms.

The fix is either:
a) Don't error in the addons-server API; interpret an unsupported platform parameter as 'All'
b) addons-frontend catches the API error and does something - e.g. redirects to https://addons.mozilla.org/en-US/firefox/search/?q=blah&appver=59.0.2
( c) wonfix )

@landryb
Copy link

landryb commented May 1, 2018

'OpenFoo' is invalid, 'OpenBSD' is a valid platform, it's just that AMO only supports/cares about Tier1. I would be fine with fallbacking to All for non-tier1.

c) wontfix ? really ?

@jvillalobos
Copy link

Given the direction we're moving towards with WebExtensions, I think we should drop the platform parameter from the Add-ons Manager search (cc @ddurst). That doesn't address this issue for all existing clients, though.

I would favor (b), since I think the API should do the "right" thing as much as possible.

@diox
Copy link
Member

diox commented Sep 25, 2018

I'm not sure how much that helps us yet, but we're moving towards dropping platform and just using applications - which would be firefox or android, and already in the URL (that's the part after the locale at the beginning).

@stale
Copy link

stale bot commented Oct 8, 2019

This issue has been automatically marked as stale because it has not had recent activity. If you think this bug should stay open, please comment on the issue with further details. Thank you for your contributions.

@stale stale bot added the state:stale Issues marked as stale. These can be re-opened should there be plans to fix them. label Oct 8, 2019
@landryb
Copy link

landryb commented Oct 10, 2019

merge with #11563 ?

@stale stale bot removed the state:stale Issues marked as stale. These can be re-opened should there be plans to fix them. label Oct 10, 2019
@stale
Copy link

stale bot commented Apr 7, 2020

This issue has been automatically marked as stale because it has not had recent activity. If you think this bug should stay open, please comment on the issue with further details. Thank you for your contributions.

@stale stale bot added the state:stale Issues marked as stale. These can be re-opened should there be plans to fix them. label Apr 7, 2020
@landryb
Copy link

landryb commented Apr 7, 2020

@Stale: issue still stands.

@stale stale bot removed the state:stale Issues marked as stale. These can be re-opened should there be plans to fix them. label Apr 7, 2020
@stale
Copy link

stale bot commented Oct 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. If you think this bug should stay open, please comment on the issue with further details. Thank you for your contributions.

@stale stale bot added the state:stale Issues marked as stale. These can be re-opened should there be plans to fix them. label Oct 4, 2020
@jbeich
Copy link

jbeich commented Oct 4, 2020

Can someone tag this issue to avoid spam every 6 months? I can still reproduce on DragonFly (BSD).

addons/.github/stale.yml

Lines 14 to 22 in cc94359

exemptLabels:
- "contrib: maybe good first bug"
- "contrib: good first bug"
- "contrib: welcome"
- "component: security"
- "state: blocked"
- "state: blocked by upstream"
- "state: pull request ready"
- "neverstale"

@stale stale bot removed the state:stale Issues marked as stale. These can be re-opened should there be plans to fix them. label Oct 4, 2020
@eviljeff
Copy link
Member Author

eviljeff commented Oct 5, 2020

The issue is stale, regardless of the tags or status of it - no-one is working on it and it won't suddenly start being worked on anytime soon. If someone is willing to step up and contribute a fix then we can look at it, otherwise it may as well stay closed.

#708 (comment) pointed to the fix being b) so probably best to dupe this issue with #11563 anyway and work on it there.

@stale
Copy link

stale bot commented Apr 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. If you think this bug should stay open, please comment on the issue with further details. Thank you for your contributions.

@stale stale bot added the state:stale Issues marked as stale. These can be re-opened should there be plans to fix them. label Apr 18, 2021
@stale stale bot closed this as completed Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:stale Issues marked as stale. These can be re-opened should there be plans to fix them.
Projects
None yet
Development

No branches or pull requests

5 participants