VS Code plugin

[StevenClontz]

• The plugin should be a web extension and made available as easily as possible when using [a fork of] https://github.dev/pi-base/data
  • It's possible we find another essential request below to be out of scope for this, in which case a pi-base/data Codespace configuration could be considered instead
• Markdown files should open both source and a useful preview of that source (incorporating YAML frontmatter)
• Hovering over IDs in source should reveal info like title on the relevant item, and offer links to those files in the editor or to the corresponding page at https://topology.pi-base.org
• "type checking" and completion/suggestions for YAML frontmatter
• GUI to create new objects/props/thms that come with approrpiate boilerplate and are named with a timestamp something like T20230306150539.wip.md to prevent collisions. (Of course, I'd like to automate converting those to permanent IDs upon acceptance somehow...)

[jamesdabbs]

@StevenClontz – do you use VSCode locally at all, or just entirely through Codespaces? I've cut a revamped version of this, and would appreciate if you could try to install it and let me know:

• Does it install, or do you get an error?
• Does it work? (Right now it's just doing some basic ID and external reference linking)

[StevenClontz]

I use the web version exclusively (eating the dogfood, don't want to only know how to do things that require others to install things). I'll check this out

[StevenClontz]

Tried this first, but it's not available. (Would be really nice as VS Code for Web is quicker to spin up than a Codespace.)

Trying a codespace now.

[StevenClontz]

Hey neat.

Trying to open files causes an error (note backslashes):

[jamesdabbs]

Alright, I made a little bit of progress getting this working in github.dev with the new release. Feel free to give that a try. Next-up issues:

• Understand why the hover / id references aren't working on the web
• Figure out the right way to handle filesystem / path joining (per the \ issue above)

[StevenClontz]

The extension can be installed, but doesn't seem to have any effect:

[jamesdabbs]

@StevenClontz – try again? (I fixed a bug where the P3 lookups that were expecting P000003)

[StevenClontz]

So cool.

Now I need to get this rigged up by default for everyone...

[jamesdabbs]

I saw pi-base/data@dd40b6f ... I think pi-base/data#655 is also worth adding?

[jamesdabbs]

@StevenClontz – 😎 Live on https://github.dev/pi-base/data now

I still need to get the click-to-follow-reference working here. (All of these errors were related to Codespaces using a vscode-vfs:// uri scheme instead of file:// as it is locally.) Once that's done, I'm inclined to get this POC merged in to this repo as a new package and start iterating from there. Sound good?

[StevenClontz]

I'm inclined to get this POC merged in to this repo as a new package and start iterating from there. Sound good?

All good with me.

BTW I think pi-base/data@dd40b6f was what got things working in github.dev and pi-base/data#655 was what was needed for Codespaces.