Implement Dart 3 recods

[tenhobi]

Implement support for record types.

Note: we might merge it even before we have Dart 3 since the analyzer already can know the record type.

[Abdulrasheed1729]

To implement for the Dart 3 records, in my opinion, I think it would be better to first convert it to a map first for it to work, for example like a toMap() extension function,

final record1 = (2, 'hello', true);
print(record1.toMap()) // prints {'$1': 2, '$2' : 'hello', '$3' : true}

but it seems difficult to implement. And it is almost impossible according to what is here.
Or is there something I'm missing?

[tenhobi]

I haven't looked much into it, but I initially thought we could get positional and named things out of it, similar to the constructor, and do something about it?

[Abdulrasheed1729]

Oh, yes, thanks, I just found out there is RecordType 😄 in the anlayzer library with the namedFields and positionalFields getters, I will try to get something out of that 👍

[Abdulrasheed1729]

I've been trying to mess around with some things, what if we have the type Record use as a primitive type 🤔? Like what is in this extension.

extension DartTypeExtension on DartType {
  bool get isPrimitiveType =>
      isDartCoreNum ||
      isDartCoreInt ||
      isDartCoreDouble ||
      isDartCoreString ||
      isDartCoreBool ||
      isDartCoreEnum ||
      isDartCoreSymbol ||
      isDartCoreRecord;
}

And have something like this

@AutoMappr([
  MapType<RecordHolderDto, RecordHolder>(),
])
class Mappr extends $Mappr {}

class RecordHolder {
  final Record value;

  RecordHolder(this.value);
}

class RecordHolderDto {
  final Record value;

  RecordHolderDto(this.value);
}

I still doubt if this is right, but I just want show it, before I create a PR.

[tenhobi]

I think the difference between primitives and iterable/map right now is that we pass a primitive just like that, and we map each part of iterable/map.

Meaning in the Iterable I can have List<UserDto> -> List<User>, in Map, I can have Map<KeyDto, ValueDto> -> Map<Key, Value>, and in Record, I can have (UserDto, AddressDto, school: SchoolDto, ...) -> (User, Address, school: School, ...).

I am not sure how the records mapping should work exactly either because we didn't use it yet. :D That is what this issue is about -- do research and probably do it similarly to list/map mappings. It's for sure a tricky issue to do.

[Abdulrasheed1729]

Yes, it is quite tricky one to implement. I will make more findings and try to imitate that of map/list.
Thanks for the feedback.

[tenhobi]

Will be available in v2