Hacking on the explorer graphql API (and frontend)
# development
c
Hacking on the explorer graphql API (and frontend)
image.png
w
Hey, unrelated to this exactly - but could the Explorer be put into the VS Code plugin?
c
frontend re-work, using svelte rather than React, gives a lot less and easier to work with code šŸ™‚ (theme/colors tbd)
@wide-midnight-78598 care to elaborate slightly, Iā€™ve no clue what that is/what it would look like..
w
Me neither, but having a Pants documentation explorer directly in VS Code seems useful. Like, a tree-view menu, which goes through all available subsystems, goals, etc
c
Ah, yea sure. as long as the backend server is up and running, the vs code plugin could issue graphql queries to get the data to present somehowā€¦
šŸ‘ 1
w
Awesome
c
Maayybeeā€¦ vs code can present something like an iframe..? in which case you could pull in the explorer ui directly in vscode.
would reduce duplicated efforts in the areaā€¦
unless thereā€™s good frameworks in place already, as the api will be there regardlessā€¦
w
So, the docs themselves would be whatever the VS Code equivalent of an iframe is (which I believe they have). The side nav part, if it can hook into auto-complete, would be pretty slick
Err, auto-find, or whatever that command palette is called
c
we can have pretty slick search features in the api, to support feeding the data we want to whereever, Iā€™m all into that šŸ™‚ (not using VS code myself thoughā€¦ so I would stay on the backend side of the fence šŸ˜› )
šŸ‘ 1
right now, Iā€™ve only added pretty basic regexp filtering on names and the like + limit number of results returned, just to have something.
Subsystem docsā€¦ šŸ˜‰ This will include docs for any private plugins etc you may have.. cc @bitter-ability-32190
ā€œpeekā€ info from your project (and a terrible color theme.. šŸ˜› )
image.png