-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(shared): toDisplayString toString override support #4337
fix(shared): toDisplayString toString override support #4337
Conversation
Could you leave the reviews on the other PR instead of creating a new one, please? |
@edison1105 made a great pr, I worked on a fix before I saw your pr, and I hope that my PR did not offend you. @posva I would have appreciated you actually providing a review on this pr instead of closing it. |
It’s ok. This PR covers more cases. Actually, I don't know if it's worth to check the override toString. Like @posva commented on other PR. The point is: should we put toDisplayString farther?let’s discuss it on other PR. |
Once again, this is nothing personal, it's about respecting the original author's PR and making it easier to review for the maintainers as well (1 PR instead of 2 PRs) as well as discussing changes. You also seem to only see the things from your perspective, please also consider other people's perspectives 🙂 In this specific scenario, @edison1105's PR seems to be closer to what needs to be covered. |
haha "nothing personal", is like saying "I don't mean to offend but". I actually do hope its personal, and that other people are not treated the same way. that is my perspective. |
I incorporated the |
fix: #4334
fix for the case object without
toString
for example:handle the case that
toString
is non invokable, and use the JSON formatter for that caseimproving on: #4335