anvilco/spectaql

Copy button in the query code block missing

icymaru opened this issue · 12 comments

Just simple button for easy copying
image

Also, is it possible to expand the query input here instead of having a separate code block?

@icymaru thanks for using SpectaQL and writing in!

I like the idea of having a copy button for sure.

is it possible to expand the query input here instead of having a separate code block?

Could you explain a bit more what you mean here?

@newhouse I would like to take up this, could you assign it to me please

@ravisoni01 if you feel up to it, give it a whirl.

I'm not up to speed with the "best" way to implement copy buttons these days, but I assume that you are?

Can you describe your approach maybe?

@newhouse My approach is: First, I will make a copy button beside the query or mutation, and on the click of the button, I will call a function, and on the function call, I will save the query or mutation data into the clipboard.

@ravisoni01 go for it!

@newhouse I don't find proper documentation for running the project in my local . Can you please guide me on how I can run in my local

@newhouse I don't find proper documentation for running the project in my local . Can you please guide me on how I can run in my local

After cloning and running yarn install:

yarn develop /path/to/your/config.yml

Is probably the best way to develop locally. It will run a local server serving the website, and changes should trigger a rebuild where you can then refresh the page and see the results.

yarn develop /path/to/your/config.yml

@newhouse Could you please give me an idea of where I can get this path? I don't get the proper idea about this.

If you have been using SpectaQL, somewhere you have a config file, no? It is required.

If you don't have the one your organization is using, you can try just using the example one: yarn develop ./examples/config.yml

@newhouse I'm getting this error ''npm' is not recognized as an internal or external command and I tried all the possible solutions to solve this error for the past week, but I didn't get a solution to this error.

@ravisoni01 I'll handle this PR sometime then.

If you want to provide any useful code, etc, here, please do.