feat: introduce experimental full nameof support

[latonz]

introduce experimental full nameof support

Description

Introduces experimental full nameof support.
See #401.

This would allow simpler MapProperty attributes for nested properties:
[MapProperty(nameof(@A.B.C), nameof(@D.E.F)] would be the same as [MapProperty(new[]{nameof(A.B), nameof(A.B.C)}, new[]{nameof(D.E), nameof(D.E.F)}].

Checklist

• The existing code style is followed
• The commit message follows our guidelines
• Performed a self-review of my code
• Hard-to-understand areas of my code are commented
• The documentation is updated (as applicable)
• Unit tests are added/updated
• Integration tests are added/updated (as applicable, especially if feature/bug depends on roslyn or framework version in use)

[TimothyMakkison]

Nice, what made you reconsider this?

I'm not sure if it's possible, but is it possible to check for and warn the user when a qualified namespace is used?

[latonz]

@TimothyMakkison this is just an experiment 😊 I think the current solution is really tedious DX, however I'm not yet convinced by this solution. I just wanted to poke around and see what it gets. It is still far from ready to be merged, there is still a lot to consider and work out. Not sure if it should relay on the @ prefix, how to handle the namespace thing, ..., ... Not sure yet if all of this can be worked out with the existing roslyn APIs.

[TimothyMakkison]

I thought the @ symbol is a pretty clever solution - it prevents accidental usage and indicates somethings different.

The namespace thing isn't a big deal. Hopefully the error and documentation would inform people.
Perhaps when a lookup fails mapperly could scan all available assemblies and types looking for a matching namespace. Not sure how slow this is

[codecov]

Codecov Report

Merging #518 (fbb4d49) into main (630fd17) will decrease coverage by 0.12%.
Report is 2 commits behind head on main.
The diff coverage is 85.59%.

@@            Coverage Diff             @@
##             main     #518      +/-   ##
==========================================
- Coverage   90.90%   90.79%   -0.12%     
==========================================
  Files         170      171       +1     
  Lines        5905     5997      +92     
  Branches      754      764      +10     
==========================================
+ Hits         5368     5445      +77     
- Misses        371      377       +6     
- Partials      166      175       +9     

Files Changed	Coverage Δ
...scriptors/InlineExpressionMappingBuilderContext.cs	95.91% <ø> (ø)
...Riok.Mapperly/Descriptors/MappingBuilderContext.cs	100.00% <ø> (ø)
...iptors/MappingBuilders/DictionaryMappingBuilder.cs	90.82% <ø> (ø)
.../MappingBuilders/DirectAssignmentMappingBuilder.cs	100.00% <ø> (ø)
.../Descriptors/MappingBuilders/EnumMappingBuilder.cs	85.28% <ø> (ø)
...tors/MappingBuilders/EnumToStringMappingBuilder.cs	100.00% <ø> (ø)
...iptors/MappingBuilders/EnumerableMappingBuilder.cs	95.00% <ø> (ø)
...escriptors/MappingBuilders/MemoryMappingBuilder.cs	88.46% <ø> (ø)
...uilders/NewInstanceObjectPropertyMappingBuilder.cs	91.17% <ø> (ø)
...criptors/MappingBuilders/NullableMappingBuilder.cs	92.85% <ø> (ø)
... and 47 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[github-actions]

🎉 This PR is included in version 3.1.0-next.1 🎉

The release is available on:

• GitHub release
• v3.1.0-next.1

Your semantic-release bot 📦🚀

[TimothyMakkison]

Nice, I'll be interested to see what people think of this 😅

Out of curiosity, why did you move the parsing logic into AttributeDataAccessor.CreateMemberPath, didn't CallerArgumentExpressionAttribute work?

[latonz]

CallerArgumentExpressionAttribute does not work, because the Roslyn apis resolve only the compile type value provided to the constructor. Mapperly then constructs the PropertyMappingConfiguration type via reflection. Since it is initialized via reflection the CallerArgumentExpressionAttribute cannot be applied.

[github-actions]

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

• GitHub release
• v3.1.0

Your semantic-release bot 📦🚀