Custom toString methods for data classes about freezed HOT 9 CLOSED

That's hardly feasible.
The class user-defined is implemented not extended.

The closest we can get is:

@immutable
abstract class ClubId with _$ClubId {
  const ClubId._();
***

It looks ugly with additional 'const ClubId._();' line

What if about freezedNoToString attribute for example:

@freezedNoToString
abstract class ClubId with _$ClubId {
  const factory ClubId(String value) = _ClubIdDataClass;

  @override
  String toString() {
    return 'ClubId#$value';
  }
}

from freezed.

That's hardly feasible.
The class user-defined is implemented not extended.

The closest we can get is:

@immutable
abstract class ClubId with _$ClubId {
  const ClubId._();
  const factory ClubId(String value) = _ClubIdDataClass;

  @override
  String toString() {
    return 'ClubId#$value';
  }
}

and then Freezed would try to extend this class

from freezed.

That's still not feasible.

As I said, the class is implemented not extended. This doesn't allow user defined methods.

from freezed.

As I said, the class is implemented not extended. This doesn't allow user defined methods.

And what about use different attribute for the different generation to extend this class as I told about?

toString methods became unreadable with lists and complex objects..

from freezed.

I would very much prefer working on the readability instead.

The toString could be made to be multi-line instead

from freezed.

The toString could be made to be multi-line instead

How it could be readable with hundred items List<Item> for example?

from freezed.

It can be shown last in the toString, or truncated like list: [0, 1,..., 42]

from freezed.

list: [0, 1,..., N] is a bit better then print big lists, however it could be big objects where could be nice toString just Id or some short info

from freezed.

Closing in favor of #83

from freezed.