Improve script parsing scope to support dynamically added attributes

Sometimes, I want to have enumeration in code bind to script attributes. It turns out, I can have it with something like this:

const FXType = {
    UNIT_SPAWN : 'unit-spawn',
    UNIT_DESTROY : 'unit-destroy',
    IMPACT_FIREBALL : 'impact-fireball',

    getKeyArray : function() {
        const value = []
        for (const k in FXType) {
            if (k === 'getKeyArray') continue;
            value.push(k)
        }
        return value
    }
}

FXType.getKeyArray().forEach(v => {
    Fxpool.attributes.add(v, {type : 'asset', assetType : 'template'})
})

this is fine and dandy. However, if I later want to have a enum attribute in some other script:

SomeScript.attributes.add('impactFX', {type : 'string', enum : FXType.getKeyArray().map(v => { return {[v] : v}})})

I get this:

would be so helpful to bind this enum value somewhere else, in fact, in a lot of places. That would help to improve quality of code in small to medium size projects by a huge margin.