stagep

Yes, I am using Mapster.Tool with gRPC and repeated fields. For example: ``` repeated EmploymentLevelMessage employment_levels = 8; ``` and this is the .proto for EmploymentLevelMessage ``` message EmploymentLevelMessage {...

I now recall that I was getting the exception "Cannot convert immutable type, please consider using 'MapWith' method to create mapping" when I used the latest pre-release version that supported...

@DocSvartz @DevTKSS reviewing the documentation is going to take a while. We should move forward with publishing as it cannot be any worse that it currently is, as it is...

@DocSvartz This should be added to the documentation. I will put in some time over the weekend to review the issues where I need to respond. I have to understand...

@roohial57 I agree with you 100% that there is ambiguity. It is like asking what is zero divided by zero. In mathematics, we say this is indeterminate. In the non...

@DocSvartz @roohial57 I realize now that we should prioritize returning the expected result when mapping to an existing record, over introducing a Result concept. I see 3 options. 1. Introduce...

@DocSvartz @DevTKSS I believe that we simply have to decide that when we map (using map as the generic term for what Mapster does) and we map to a record,...

I 100% agree and missed the void versus return type method differentiation. The void method cannot mutate, the return method returns a new record with "updated" values. We will make...

@DevTKSS the method that has no return type / returns void (however you look at it) has to throw an exception. The method that returns the type (the destination type)...

Personally, I don't fell that I should be able to approve Mapster code PRs but that @andrerav and @DocSvartz can. However, if we determine how the documentation is to be...