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
Currently each generator may have a specific name. This is not very elegant since
Only top-level generator names are useful, but any generator may have a name.
All the generator objects have a Some[String] attribute for storing their name, and they don't really them.
By nature, the notion of "name" is not related to the notion of generator. The names are only used to refer to "external" generators in JSON documents storing such generators.
I propose to remove the "name" attribute from the generator objects, and to consider their name as a meta-information. From the perspective of JSON configuration documents, the "generators" attributes will therefore become:
"generators": {
"name-here": {…}
}
The text was updated successfully, but these errors were encountered:
Currently each generator may have a specific name. This is not very elegant since
I propose to remove the "name" attribute from the generator objects, and to consider their name as a meta-information. From the perspective of JSON configuration documents, the "generators" attributes will therefore become:
The text was updated successfully, but these errors were encountered: