Mark Lundin

> @marklundin does this include the nested seralizable objects? It does, but this isn't included in the example. Will update

Thanks @Maksims, good to have your input. > 1. How a JSON type is defined? The JSON type becomes a complex type, this could be defined through the jsdoc `@type...

> A side question, how will these attributes look in typedoc? Will they be among other properties/accessors? Tags like type and enum are already so would be handled as-is. It...

> > There's also some requests with the existing system where users want to share common data between scripts like an enum listing of colours or a particular JSON format...

@Maksims Coming back to you earlier point; ```javascript var Example = pc.createScript('example'); Example.attributes.add('chunks', { type: 'json', array: true, schema: [{ name: 'name', type: 'string' }, { name: 'shader', type: 'asset',...

Could you provide a repro? You should be able to set a script not to preload and see the attributes parsed in the inspector

I suggest we add this to the documentation and additionally ensure that any script added as a loading screen is marked as no preload

> What would be the impact to users in terms of migrations or API changes? `pc.createScript()` will still work and return a `ScriptType` which should function in the same way....

> Can we provide a few examples of old-vs-new ways for most common use cases? As I understand, this is fully compatible with the current ScriptComponent system and can mix...

Thanks @AlexAPPi, you've hit on an important point. When an ES6 class members is defined, it is non configurable. Currently ScriptAttribute attempts to redefine the member using `Object.defineProperty` which effectively...