GithubHelp home page GithubHelp logo

Comments (4)

tvvignesh avatar tvvignesh commented on May 5, 2024 3

@daniman Hi. Sorry for the late reply. Nice to see that you have a lot of them already planned.

Regarding Templating, I was suggesting something like this: https://support.insomnia.rest/article/18-environment-variables where you can have environment variables either in the URL or the Header or the GraphQL variables so that you can just change one place and have it reflect in all the other places. Postman also has something similar here: https://learning.postman.com/docs/sending-requests/variables/ (Looks like its called environment variables πŸ€” )

For Export/Import (You can take this low on priority as it will take a lot of effort to implement), I wanted to mainly have the flexibility to switch between multiple tools like Insomnia, Postman or Postwoman (atleast 1 to go with since Apollo GraphQL is hosted in Cloud). Something like this: https://support.insomnia.rest/article/52-importing-and-exporting-data
The main concern for this is that if I have all the queries and mutations saved in Apollographql and I want to use any other tool to do the query or mutation, I have to end up copy pasting all of them into the tool like insomnia or postman and even organize them all again. So, if I have some sort of importer or exporter to insomnia, postman or postwoman, it will make the job easier in the future to either import from or export to these tools.

Yup. I already use the Apollo VSCode extension for Federation, intellisense and autocomplete. I was wondering if you can even have the entire Apollo Studio experience right within VSCode so that there is no context switching. VSCode provides Webviews where you can embed the user interfaces: https://code.visualstudio.com/api/extension-guides/webview

These were just a few things which I thought of. Will share more thoughts as I try more.

from apollo-studio-community.

daniman avatar daniman commented on May 5, 2024 1

Hi @tvvignesh! Thank you for the incredible thoughtful feedback here πŸ™

  • Saved query collections are absolutely on our mind. We have a couple other priorities at the moment, but I'm very much hoping we're able to tackle this some time in the next few months. It's been on our wish list since the beginning of the Explorer project, and we take a lot of inspiration from Postman and Insomnia.
  • Templating –– I'm curious how you imagine this would work. Could you share more info on the idea please?
  • Export/Import –– curious if you have ideas here other than a few copy/paste helpers?
  • VS Code extension –– curious which parts you'd want to see there? We do already have the extension that provides intellisense and autocomplete.
  • Embedding –– very much on our minds, but not a short term thing as it's pretty complicated.

We're currently working on honing it as a hosted tool, because pulling it out of Studio at the moment would also be quite complicated.

from apollo-studio-community.

FluorescentHallucinogen avatar FluorescentHallucinogen commented on May 5, 2024 1

Re ability to use it as VSCode extension, see #9. πŸ˜‰

from apollo-studio-community.

papollosc avatar papollosc commented on May 5, 2024 1

Hi @tvvignesh πŸ‘‹ Thank you for your feedback. Wanted to provide an update:

  1. Saving queries and mutations and organizing them in folders: We recently released this for Explorer! Please check out the blogpost and let us know what you think!
  2. Templating: Wondering if you had a chance to try out our preflight scripts feature that was rolled out beginning of this year.
  3. Export and import queries and mutations: We are actively thinking about this, now with the first release of operation collections - being able to export collections out of Explorer. Importing operations to Explorer is also a great idea and I will take that as a feature request for our roadmap.
  4. Embedding: We also rolled this out late last year! At least a first version that works with public graphs. We are actively working on making it happen for graphs that are gated behind Studio auth. Would love to hear your thoughts on this πŸ™

For the VSCode webviews, that is a great suggestion and I will take that as a feature request. I am closing this issue for now. Please do provide further feedback/suggestions/comments as you (hopefully) dig into our recent feature releases. We truly appreciate it!

from apollo-studio-community.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.