Critiques pour Altair GraphQL Client
Altair GraphQL Client par Samuel
Avis de Samuel
Réponse du développeur
mis en ligne : il y a 6 ansThanks for pointing that out. We don't need that permission for the addon to work actually :)
21 notes
- Noté 1 sur 5par Guilherme, il y a 2 ans
- Noté 5 sur 5par chmelik, il y a 2 ans
- Noté 4 sur 5par JLuc, il y a 2 ans
- Noté 5 sur 5par Pei-lun, il y a 2 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 17569738 de Firefox, il y a 3 ans
- Noté 4 sur 5par Joe, il y a 4 ansThe previous revision of my review was not kind, because the extension appeared not to be working. After reading the other reviews mentioning access to "all data for all sites", I wondered if it could be that I was attempting to use the extension in a private window, which was the issue. So, although Firefox will ask you if the extension should be available in private windows, and even though you allow it, this extension still does not appear to work in private windows. It does, however, appear to work in non-private (public?) windows.
- Noté 4 sur 5par Antonio Perez Caballero, il y a 5 ans
- Noté 3 sur 5par Mitch, il y a 5 ans
- Noté 4 sur 5par Utilisateur ou utilisatrice 15626011 de Firefox, il y a 6 ansBEWARE!
New versions of this extension requires access to "all data for all sites". I am unable to find an explanation for why this is required in the release notes or on their github page. This seems extremely fishy, and I am therefor uninstalling the extension out of caution.Réponse du développeur
mis en ligne : il y a 6 ansFear not! Altair has always requested permissions for all sites but they were removed, and then re-added at v2.4.3. This is required to allow Altair send requests to your domain without getting CORS errors which is the default behavior. After the permissions were removed, there were several reported issues of Altair not working (e.g. https://github.com/imolorhe/altair/issues/1136). Of course these issues were resolved after re-adding the permissions in v2.4.3.
You can see the relevant commit trails:
Removed permission (v2.4.0): https://github.com/imolorhe/altair/commit/a0cd9fad9bdaba65966c12c8aa5fad409efdfd3c
Re-added permission (v2.4.3): https://github.com/imolorhe/altair/commit/2802c9429ebcd571ca046820dd74f2f893670fb2
You can read more on why these permissions are required here: https://developer.chrome.com/extensions/xhr
Of course if you still feel that the permissions are extremely fishy, you're welcome to use the desktop apps instead, or perhaps host Altair on your domain using one of the available integrations: https://altair.sirmuel.design/docs/integrations
Sorry for the confusion! - Noté 5 sur 5par Utilisateur ou utilisatrice 15056078 de Firefox, il y a 6 ansEyyy, thanks for the response! I'll use the desktop client :)
~~~
This has been really useful, but the new permissions ('data on all sites') are sketching me out! Maybe I just read too many stories of popular addons getting bought by spyware companies...Réponse du développeur
mis en ligne : il y a 6 ansFear not! Altair has always requested permissions for all sites but they were removed, and then re-added at v2.4.3. This is required to allow Altair send requests to your domain without getting CORS errors which is the default behavior. After the permissions were removed, there were several reported issues of Altair not working (e.g. https://github.com/imolorhe/altair/issues/1136). Of course these issues were resolved after re-adding the permissions in v2.4.3.
You can see the relevant commit trails:
Removed permission (v2.4.0): https://github.com/imolorhe/altair/commit/a0cd9fad9bdaba65966c12c8aa5fad409efdfd3c
Re-added permission (v2.4.3): https://github.com/imolorhe/altair/commit/2802c9429ebcd571ca046820dd74f2f893670fb2
You can read more on why these permissions are required here: https://developer.chrome.com/extensions/xhr
Of course if you still feel that the permissions are extremely fishy, you're welcome to use the desktop apps instead, or perhaps host Altair on your domain using one of the available integrations: https://altair.sirmuel.design/docs/integrations
Sorry for the confusion! - Noté 4 sur 5par Utilisateur ou utilisatrice 14801363 de Firefox, il y a 6 ansQueries, mutations, subscriptions, Headers are all saved for convenience. So when you get back later, you can start from what you've done.
One drawback compared to Playground is that Altair does not support multiple schema docs page. - Noté 5 sur 5par Utilisateur ou utilisatrice 15321375 de Firefox, il y a 6 ans
- Noté 5 sur 5par torunar, il y a 6 ans
- Noté 5 sur 5par nmarier, il y a 6 ansThe extension is beautiful and has every feature one could want. The only concern I have is permissions. I'm not sure why this add-on would need to access my data for all sites.
Réponse du développeur
mis en ligne : il y a 6 ansThanks for pointing that out. We don't need that permission for the addon to work actually :) - Noté 5 sur 5par Utilisateur ou utilisatrice 13070411 de Firefox, il y a 6 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 13839546 de Firefox, il y a 6 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 14540431 de Firefox, il y a 7 ansThis is pretty good, but why do I have to click "reload docs" when the API changes? GraphQL APIs are supposed to change all the time, please make it reload the docs immediately. Also the app will always be online to do queries.
Réponse du développeur
mis en ligne : il y a 7 ansThere is no mechanism to reload the docs when the APIs are updated, except maybe a polling mechanism which isn't optimal. You should create an issue on Github for this so that there can be better discussions around it.
UPDATE: There is such a mechanism now. The X-GraphQL-Event-Stream header allows you specify a stream URL that your server can use to notify Altair of changes and reload the docs for you. - Noté 5 sur 5par Sandy, il y a 7 ansGreat GraphQL tool for Firefox. Constant improvements, and super easy to use and very quick to respond to issues.
Been using it for a few months now and makes my GQL work easy.