hakowork/rojo
3
0
Fork 0
mirror of https://github.com/rojo-rbx/rojo.git synced 2026-10-20 17:41:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Rename RbxItem -> RbxInstance

Browse source
This commit is contained in:
Lucien Greathouse 2018-01-03 16:01:48 -08:00
parent f00152a9ac
commit d8bcbee463
7 changed files with 24 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

8
DESIGN.md
View file

@ -6,12 +6,12 @@ This is a super rough draft that I'm trying to use to lay out some of my thought
### POST `/read`
Accepts a `Vec<Route>` of items to read.
Returns `Vec<Option<RbxItem>>`, in the same order as the request.
Returns `Vec<Option<RbxInstance>>`, in the same order as the request.
### POST `/write`
Accepts a `Vec<{ Route, RbxItem }>` of items to write.
Accepts a `Vec<{ Route, RbxInstance }>` of items to write.
I imagine that the `Name` attribute of the top-level `RbxItem` would be ignored in favor of the route name?
I imagine that the `Name` attribute of the top-level `RbxInstance` would be ignored in favor of the route name?
## CLI
The `rojo serve` command uses three major components:
@ -21,7 +21,7 @@ The `rojo serve` command uses three major components:
### Transform Plugins
Transform plugins (or filter plugins?) can interject in three places:
* Transform a `VfsItem` that's being read into an `RbxItem` in the VFS
* Transform a `VfsItem` that's being read into an `RbxInstance` in the VFS
* Transform an `Rbxitem` that's being written into a `VfsItem` in the VFS
* Transform a file change into paths that need to be updated in the VFS watcher