ChromeiQL
Extension Actions
CRX ID
fkkiamalmpiidkljmicmjfbieiclmeij
Status
- No Privacy Policy
- Live on Store
Description from extension meta
Chrome app wrapper for the GraphiQL tool
Image from store
Description from store
Simple extension wrapper around the great GraphiQL IDE allowing it to work with any GraphQL endpoint of your choosing.
As long as you are authorized to send requests to the endpoint from your current browser session (cookies are set etc.) you are good to use ChromeiQL.
New in 1.0
==
* Upgraded GraphiQL to version 0.11.3 with history, prettify, faster result pane and better highlighting
Latest reviews
- Максим П
- Всё ок до тех пор, пока тебе не потребуется добавить новый заголовок в запрос. Этот инструмент такое не умеет. Благо, есть другие расширения
- marcel bok
- i havn't used it yet but have high expecgagiojs
- marcel bok
- i havn't used it yet but have high expecgagiojs
- yl d
- Nice
- yl d
- Nice
- Srini R (rsrini7)
- Wow!! Saved a lot of time. Thanks a lot.
- Srini R (rsrini7)
- Wow!! Saved a lot of time. Thanks a lot.
- Taki F
- all things you eed to test your graphql application
- Taki F
- all things you eed to test your graphql application
- Anonymous
- Simply the best ;-) Thank you.
- Nghiệp Thân
- It will be better if you implement feature insert value into request header. In my case, I need to insert authorization into header but I can't. Hope you will update soon. Anw, thanks for your effort.
- Nghiệp Thân
- It will be better if you implement feature insert value into request header. In my case, I need to insert authorization into header but I can't. Hope you will update soon. Anw, thanks for your effort.
- Pasi Salo
- Not very useful since you cannot define any auth headers
- Pasi Salo
- Not very useful since you cannot define any auth headers
- Subhajit Das
- Great tool
- Subhajit Das
- Great tool
- Josiah Petersen
- Simple to use and overall functional. Fairly annoying issue is that it seems to crash every time you try to copy within the extension (like a result or URL).
- night4lover
- Good tools, no problem with setup. it just worked!! <ctrl> <space> for autocomplete hints.
- night4lover
- Good tools, no problem with setup. it just worked!! <ctrl> <space> for autocomplete hints.
- Qing Zheng
- Very good. Can you add support to save/modify a named query?
- Qing Zheng
- Very good. Can you add support to save/modify a named query?
- Jonathan D'Orleans
- Working like a charm! Many thanks for the version update. P.S. I couldn't find your extension in the Store at first because I was looking for the keyword 'graphql' and it didn't show ChromeiQL. Consider adding this keyword in the description too.
- Jonathan D'Orleans
- Working like a charm! Many thanks for the version update. P.S. I couldn't find your extension in the Store at first because I was looking for the keyword 'graphql' and it didn't show ChromeiQL. Consider adding this keyword in the description too.
- Kevin Russon
- This tool is amazing for GraphQL testing. I love the recent updates that saves a history of my recent queries.
- Kevin Russon
- This tool is amazing for GraphQL testing. I love the recent updates that saves a history of my recent queries.
- Дима Лобурец
- Awesome!
- Дима Лобурец
- Awesome!
- Shek Hei Wong
- Love it ,but, it is far too old... Hope the author will update this with newer versions of graphiql
- Shek Hei Wong
- Love it ,but, it is far too old... Hope the author will update this with newer versions of graphiql
- Paul Ericksen
- I'd rate a 5, but it's apparently using rather out-of-date GraphiQL code. For instance, it doesn't have the "prettify" button and won't auto-complete a node (when you ref an object but don't have any properties listed then run the query it should fill out every property for you), the documentation explorer doesn't have the ability to search... etc.
- Paul Ericksen
- I'd rate a 5, but it's apparently using rather out-of-date GraphiQL code. For instance, it doesn't have the "prettify" button and won't auto-complete a node (when you ref an object but don't have any properties listed then run the query it should fill out every property for you), the documentation explorer doesn't have the ability to search... etc.