Support fields

Describe the bug Mapping from for example System.Numerics.Quaternion is broken. I get the feeling that this might be something that’s either not spelled out enough in the documentation or something that is an oversight because people mostly deal with Properties anyway. Anyway mapping from/to fields does not work. They are completely ignored. Which is a shame because I do tend to need such mapping from time to time and I currently have to do them manually.

To Reproduce

public class Quat
{
    public float X;
    public float Y;
    public float Z;
    public float W;
}

[Mapper]
public static partial class Map
{
    public static partial Quat ToQuat(Quaternion quaternion);
}

Generated code:

    public static partial class Map
    {
        public static partial ClassLibrary1.Quat ToQuat(System.Numerics.Quaternion quaternion)
        {
            var target = new ClassLibrary1.Quat();
            return target;
        }
    }

---

Environment (please complete the following information):

• Mapperly Version: 2.6.0
• .NET Version: 7
• Target Framework: 7
• OS: Linux

Additional context

[latonz]

On a second thought and after reading @Blackclaws’s comment I think enabling field mappings by default should be fine and even expected by most of users. #346 adds support for fields. Field mappings are enabled by default and the only currently implemented way to disable them is by using MapperIgnoreTarget / MapperIgnoreSource. A next release should be published in the upcoming days including this feature.

[softlion]

A lot of devs expect consistent behaviors between different .NET features. So having a feature that behaves like Fody.PropertyChanged or System.Text.Json makes more sense in my vision of things.

The new “record” type for example is a compact syntax to create a class or struct with only properties.

I understand what you mean with mapping those structs.