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
Update the version detail API to report host_permissions #9105
Comments
I think we should hold off on this until we know what the actual need/request is. What frontend is going to display, and how - if it's just that the urls aren't omitted from the permissions block for MV3 add-ons the serializer should just return both urls and permission names in the existing |
With the filing of #14670, it looks like we're going to need this. Based on the lengthy discussion at #9104, I feel like the following are our best options:
As discussed in the other issue, I am in favour of 1. It does involve some extra processing on the client, but it also means we aren't coupling the API response to our specific UX requirements at this time. My concern with option 2 is that, if we decide to do something different with |
This is going to mix API and host permissions, which MV3 solved with the introduction of |
Note the MV2 add-ons (the vast bulk of extensions on AMO today) mix the host and API permissions, and frontend processes them to display them separately* (in the same card). So we should consider how MV2 permissions are handled too. *option 1 would, as far as a I understand it, lead to less processing on the client, because host and API permissions wouldn't need to be split out from a single list of optional permissions(?) |
Yes, but they are also all required so that makes sense.
Are they displayed separately? My understanding is that we have two sections, and for each, we have both API and host permissions. In the screenshot below, we only have host permssions (some required, some optional): And here we have both API and host permissions, all required: |
Separately on the same card. From #9104
|
I tried with MV2 and MV3 -> the detail/version endpoints return permissions , optional permissions and host permissions |
Old Jira Ticket: https://mozilla-hub.atlassian.net/browse/ADDSRV-276 |
This is a follow-up to #9104. Once we are storing
host_permissions
for MV3 add-ons, we should update the API to return those storedhost_permissions
.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: