You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although perhaps outside the scope of this project, I think it would be great to support structured data as well. Depending on what you think, we have 3 options in order to do this:
Implement the value types and very tiny nodes to work with on the core package and a separate package/profile with some extended tools
Implement it as a separate package/profile inside this repository (officially supported/maintained)
Implement it as a separate package/profile in other repository (community maintained)
I have a working example here with some examples I was working on in the last days: behave-graph/struct I also deployed them here to test the github-actions and the docs I did for this repo, but in this case just with that specific profile
I personally would prefer the 1st or 2nd option and include it in the main repository as an optional profile, same as the Scene one but it's up to you as I don't know if this makes sense.
This is great idea. I will review in more detail in the coming days.
The plan has always been to support both JSON as well as Lists and Arrays. Now the only question is whether Lists are the same as Arrays? In Unreal Engine Blueprints, sockets specify if they are arrays and what their dimensions are:
@bhouston about array vs lists, I used list because it's the naming used by the Ramda library (doc here. Probably they using lists because they allow other kind of Iterables and not just arrays, but yes, the original javascript datatype would be array.
Although perhaps outside the scope of this project, I think it would be great to support structured data as well. Depending on what you think, we have 3 options in order to do this:
I have a working example here with some examples I was working on in the last days: behave-graph/struct I also deployed them here to test the github-actions and the docs I did for this repo, but in this case just with that specific profile
I personally would prefer the 1st or 2nd option and include it in the main repository as an optional profile, same as the Scene one but it's up to you as I don't know if this makes sense.
cc @bhouston @oveddan
The text was updated successfully, but these errors were encountered: