Support Different Types of Values without using model json about rojo HOT 3 CLOSED

If we were going to do this, it should still be TestValue.IntValue.json.

IIRC though, you can set model.json to have a classname.

I'd much rather not have the type of the value created encoded in the name of the file. Especially since I'd rather have certain models be 1 JSON object instead of multiple files (which gets nasty very quickly).

from rojo.

The JSON format in .model.json files is mostly a holdover until proper rbxmx/rbxlx support is implemented. Once we have real model files (and bi-directional syncing) it won't be as big of a deal what the actual on-disk representation is.

I pushed up a prerelease for 0.4.0 that supports .model.json files. The only example right now is this file.

Long-term, I'd like to throw an error or just ignore files that can't be interpreted instead of turning them into StringValue objects like they are right now. To regain the current behavior of StringValue objects, you'd configure some optional plugin!

from rojo.

I think this use case is well-handled by JSON models as well as Rojo's rbxmx and rbxm support!

Since I don't think there's a lot of value in specifying class name via file name only, I'm going to close this issue.

from rojo.