Joel Dunham

+1 to @tbenthompson - this looks like a duplicate of https://github.com/johnpapa/vscode-peacock/issues/7

+1 I have been wanting this also. If I can figure out how to achieve this I'll propose a PR.

I think @thoroc is right this is a duplicate of https://github.com/johnpapa/vscode-peacock/issues/7

@AferraroMezrah Please read my summary of #7 here https://github.com/johnpapa/vscode-peacock/issues/7#issuecomment-1921946816 You can see that the 'location where the colour information is saved' is dependant upon VSCode itself and unless someone can...

@ncamaa I'm not sure I understand what you're suggesting. It's possible you don't understand the limitation described by https://github.com/johnpapa/vscode-peacock/issues/7#issuecomment-1921946816 If you want to see this issue resolved please pester the...

@AlexSapoznikov I think it's possible you don't understand the limitation described by https://github.com/johnpapa/vscode-peacock/issues/7#issuecomment-1921946816 - tl;dr: there is no way to tell VSCode to change the colours WITHOUT SAVING TO THE...

@AlexSapoznikov >So you are saying that you can not apply new colors without touching .vscode/settings.json? yes that's exactly what I'm saying. Please read the linked comment from #7 and peruse...

@AferraroMezrah why don't you try out what you have in mind and report back? The goal is to apply colours the way peacock does but you can't touch the file...

I agree and would like this feature also. This integration seems oriented around the case where a dev works on a repo and wants to know about basically everything that...

I would def love this. If I've got a page making a gql request that returns a particular payload I want to give it something to search for (JSON path?)...