Re: [viatra-dev] Transformation API

[Ujhelyi Zoltán <ujhelyiz@xxxxxxxxxx>]

>> About the convenience methods: it would be 'strange' to have convenience methods for the seemingly more complex multivalued case and not for the single-valued case (where I don't see a way to do it).  
>> 
>> 
> 
> I can only parse this sentence up to the first parenthesis, from then on it doesn't make sense to me.

Hi,

I try to express my concerns more clearly (and with an example as well :) ):

Gábor suggested to have convenience methods that handle ELists findable from the EMF API, e.g.:
 * method.add(method.parameters, newParameter)

This approach works well for multi-valued references (even better than my EMF-reflective implementation), however, for single-value references or attribute I see no way of implementing an API like this, e.g.:
 * method.set(method.name, "main")

My point was, it would be strange to support the seemingly more complex case with an API as mentioned before while not having something like it for the single-valued references.

Just to be clear, if someone would suggest an implementation for these single-valued case, I would consider this more like the default API instead of a convenience method, because it is that much more understandable and verifiable for the users.

Cheers,
Zoli