feat: rewrite using macros

[felangel]

With macros on the horizon, it will be possible to implement equatable using macros which will both improve the performance of equality comparisons and significantly simplify the usage.

Before

class Person extends Equatable {
  const Person({required this.name});
  final String name;

  @override
  List<Object> get props => [name];
}

After

@Equatable()
class Person {
  const Person({required this.name});
  final String name;
}

See also https://github.com/felangel/data_class which will be built on top of package:equatable.

[tienlbhoc]

This is a good news. But can you add more features:
Current:

• copyWith : seem enough, maybe change to copy (like jetpack compose to shorter)
• operator== and hashCode : seem need config like Equatable because a long response from server can check only by some fields.
• toString : I always change to string because some field need protect and list only show length so need custom option
• const : seem ok

• Need option convert class to json and json to class and need json key map example:

@Data()
class Person {

  @key("full-name")
  final String fullName;
}

can you add above feature to Equalable version for old project ?

[felangel]

Equatable is meant to just be for equality comparisons. package:data_class will implement copyWith, toString, and equality. For json serialization check out package:json and the JsonCodable macro

[rainyl]

Great, but it will be better if we can specify the properties to compare like before, sometimes we just need several props to compare.

[felangel]

Great, but it will be better if we can specify the properties to compare like before, sometimes we just need several props to compare.

In those cases you should probably just write your own operator== override since the goal of the package is to provide value based equality comparisons (which means taking all fields into account).

[rainyl]

Great, but it will be better if we can specify the properties to compare like before, sometimes we just need several props to compare.

In those cases you should probably just write your own operator== override since the goal of the package is to provide value based equality comparisons (which means taking all fields into account).

Allright, thx.

[vadrian89]

Hello Felix, i stumbled upon this issue and I noticed both you and Remi Rousselet seem to be building the same type of package. Wouldn't be more beneficial if you and him join up?