Mapping uppercase properties and case sensitivity about mapper

[nartc]

My initial thought that that would not be possible given that the library needs to ship Flatten capability. But I'll think about this a little bit more then I'll get back to you.

[nartc]

https://automapper.netlify.app/docs/usages/features/naming-convention have you checked out this docs?

[AliYusuf95]

@nartc Yes I did, the thing that I have to use a naming convention for the source/distention but in my case I don't have a fixed convention.

I thing the default behavior should map between the properties that having same name unless we specify a naming convention or the library should ship with it an implementation for such behavior.

[AliYusuf95]

@nartc for now I implemented this convention to solve my problem, but I'm not sure if it'll cover all scenarios

class FlattenConvention implements NamingConvention {
  separatorCharacter: '';
  splittingExpression: RegExp = /(^.+)/i;
  transformPropertyName(sourcePropNameParts: string[]): string {
    return sourcePropNameParts.join('');
  }
}

Mapper.withGlobalSettings({
  sourceNamingConvention: FlattenConvention,
  destinationNamingConvention: FlattenConvention,
});

[nartc]

What exactly does this naming convention do?

[AliYusuf95]

In my case, I don't want to use naming conventions for automatically mapping.
I just want to map whatever key on the source to its corresponding key in the destination and if I have customization I'll use forMember to do it.
For example if I have these classes:

class Company {
  @AutoMap()
  camelCase: string;
  @AutoMap()
  PascalCase: string;
  @AutoMap()
  snake_case: string;
  @AutoMap()
  ['Some_Complex.Key| string']: string;
}
class CompanyVm {
  @AutoMap()
  camelCase: string;
  @AutoMap()
  PascalCase: string;
  @AutoMap()
  snake_case: string;
  @AutoMap()
  ['Some_Complex.Key| string']: string;
}

I expect that mapping will work without any extra configuration.
That's what I'm trying to achieve with my FlattenConvention, and it works fine unless there is . in the keys.

[nartc]

@AliYusuf95 I see. I might be able to provide a MixedConvention mode for cases like yours. But it's gotta be a configuration because I need to keep the CamelCaseNamingConvention as default.

[nartc]

Closing this due to #243 . I won't be adding this to the current @nartc/automapper as stated in the announcement. That said, this will be available in the new version. Sorry for any inconvenience.