toString override not working

[johnnyggalt]

Describe the bug
Overriding toString does not work. I feel like I must be doing something incredibly stupid, but have boiled this down to simplest thing that should work, and it doesn't.

To Reproduce

import 'package:freezed_annotation/freezed_annotation.dart';

part 'repro.freezed.dart';

@freezed
class Repro with _$Repro {
  const factory Repro({required int foo}) = _Repro;

  @override
  String toString() => 'My custom toString';
}

void doRepro() {
  const repro = Repro(foo: 42);

  // "Instance of '_$ReproImpl'"
  final reproToString = repro.toString();
}

Expected behavior
My toString implementation should be invoked, not that of the _$ReproImpl type. Even the IDE agrees it should be invoking my implementation because go-to-definition jumps there, but nope.

This is using latest:

dependencies:
  freezed_annotation: ^2.4.4

dev_dependencies:
  build_runner: ^2.4.12
  freezed: ^2.5.7

[get6]

Do you try that this code?

@freezed
to
@Freezed(toStringOverride: false)

[johnnyggalt]

@get6 Yes, tried that (I should have mentioned in my issue). It does not make any difference.

[johnnyggalt]

I just circled back to this because I'm shipping to prod shortly, and I've identified a fix. This code does not work:

@freezed
class Repro with _$Repro {
  const factory Repro({required int foo}) = _Repro;

  @override
  String toString() => 'My custom toString';
}

This code does work:

@freezed
class Repro with _$Repro {
  Repro._();

  const factory Repro({required int foo}) = _Repro;

  @override
  String toString() => 'My custom toString';
}

So for some reason the private constructor is required.

[mansourzaki]

@johnnyggalt
check this #170 (comment)

[ChunhThanhDe]

Hi, @johnnyggalt
You can see the author's explanation here

https://github.com/rrousselGit/freezed#adding-getters-and-methods-to-our-models

[johnnyggalt]

Hi, @johnnyggalt You can see the author's explanation here

https://github.com/rrousselGit/freezed#adding-getters-and-methods-to-our-models

Yeah, but the explanation doesn't really fit my experience. The problem is that in my example, there is no compile error reported, nor is there a runtime error. Instead, the runtime behavior is not what you'd expect (the override is not called). If there was at least an error message then it wouldn't have caused me so much confusion.