Skip to content

issues Search Results · repo:ermanc/ChromeiQL language:CSS

Filter by

12 results
 (52 ms)

12 results

inermanc/ChromeiQL (press backspace or delete to remove)

GraphiQL has had new versions which add things like the much-requested support for HTTP request headers. I assume it should be pretty straightforward to upgrade chromiql to use the latest graphiql version ...
  • TSMMark
  • Opened 
    on Jul 6, 2020
  • #22

Just flagging that I can t get the extension to work with .local domains: Screenshot 2019-10-17 12 04 58 The recurrent error seems to be: chromeiql.js:61661 Refused to evaluate a string as JavaScript ...
  • sta1r
  • Opened 
    on Oct 17, 2019
  • #21

Steps 1. Open ChromeiQL 2. Type and execute a mutation 3. Close ChromeiQL 4. Open ChromeiQL 5. Type a new URL and click set endpoint Result The mutation is executed after both steps 4 and 5. This ...
  • aschmied
  • 1
  • Opened 
    on Jan 24, 2019
  • #20

How can the following syntax error be resolved: SyntaxError: Unexpected token in JSON at position 0 at chrome-extension://fkkiamalmpiidkljmicmjfbieiclmeij/dist/chromeiql.js:60748:23
  • sra-013
  • 3
  • Opened 
    on Nov 2, 2018
  • #19

Great work on the extension, I just thought it would be cool if the extension could open automatically when you try to go to a GraphQL endpoint instead of showing the usual GET query missing. message. ...
  • jahvi
  • Opened 
    on Oct 9, 2018
  • #18

Hello, I ve been playing with ChromeiQL and it s awesome. We used to include graphiql as part of our app and now we can avoid doing that. 1. Is it possible to publish this for Firefox as well? The new ...
  • ieugen
  • 2
  • Opened 
    on Sep 21, 2017
  • #13

When trying to run ChromiQL against local GQL server, getting the following error in UI: { errors : [ { message : Cannot query field \ locations\ on type \ __Directive\ . } ], ...
  • voroshkov
  • 1
  • Opened 
    on Aug 27, 2017
  • #12

When the extension is re-opened two request are sent to the endpoint on-load. This is likely due to initialization of GraphiQL fetcher property. GraphiQL... fetcher = {graphQLFetcher(endpoint)} Attempt ...
  • prasad83
  • 1
  • Opened 
    on Aug 22, 2017
  • #10

This extension is setting variables to a string before the entire request payload is stringified, instead of sending an object which is more standard.
  • bryan-havenly
  • 4
  • Opened 
    on Aug 10, 2017
  • #7

Great Tool! It would be nice if user can also define custom headers to access the endpoint like authorization header.
  • zanettin
  • 7
  • Opened 
    on May 18, 2016
  • #4
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub