Open jkomoros opened 1 year ago
The complex schema checking appears to be broken in VSCode, so #7 basically doesn't work right now, it's not obvious how to make it work, it's clear the recursive/large schema checking is falling off some cliff. It looks like other folks are having issues with adjacent problems too, e.g. https://github.com/microsoft/vscode/issues/177142 , so maybe over the next few months it will clean itself up?
But for now the editing experience is about 100x harder without schema checking and intellisense to guide you through the names of different types and what arguments they expect.
That implies that the importance of a web app editing experience is much more important.
To start, just do a very very simple webapp that allows you to edit a packet in localstorage and copy/paste it.
WrappedPacket | undefined
signature? (And why wasn't typescript complaining?)mock
in environment editor breaks it, it can't get protected key mock/seeds/
.<br>
npm run serve
seeds
(that should be assumed to be the starting location of seed files for local files)seeds
import
that loads a local (or remote) file. It stores it in remotes: {[location : PacketLocation]: {lastUpdated: <time>, packet: Packet}}
. fork
button next to packets (in the future it will include parent), even if they are readonly. Every fork is in the locals packet. Rename it for the last path component.if
, add else
, test
, then
)bar/baz
, switch the value to type seed then switch it to if
. For some reason it gives a broken/weird error message that errorsByPath doesn't currently know how to handle.memory_NAME
) so that writes only affect one of them at a time. And then retrieve them from storage at boot.packetName
and then to a dict of {lastFetched}
. And then any packet that has a value in remotes, set to non-editable and show in the seed-list as remoteseeds/
(put that in the copy in build)play
button next to specific seeds in the editorparent
(or 'fork`?) in SeedPacket top level properties to show where it was forked fromtype
to the PropertyShape and use it to set the default value for the control(optional)
(!)
next to those. Then seed-editor should pass allowedTypes to it, so it can warn before you add an illegal typeremove
button to seed and object keycloneObjectWithChange(path : ObjectPath, value : JSONValue)
that returns a clone of the object with the path changed as configured.as unknown as ThunkMiddleware...
in applymiddleware in store.ts