Skip to content

Conversation

@cserteGT3
Copy link

I implemented a pretty basic check and a simple testcase.
I have two questions:

  • Is the test case ok?
  • Should we inform the user, which is the offending output?

Closes #163.

@waralex
Copy link
Collaborator

waralex commented Feb 16, 2022

Hi @cserteGT3!

Should we inform the user, which is the offending output?

I think that would be nice. In principle, this can be understood from the backtrace, but I think that the indication in the error will be more informative

Is the test case ok?

Yep, but if you want to make it perfect, then you can check the error message :)

@cserteGT3
Copy link
Author

I changed the error message to be more verbose and added a testcase for it. :)

@waralex waralex self-requested a review February 16, 2022 21:46
@waralex
Copy link
Collaborator

waralex commented Feb 16, 2022

It looks great! Thanks a lot! I plan to release this and another fix early next week

@waralex waralex merged commit d6d4001 into plotly:dev Feb 16, 2022
@cserteGT3 cserteGT3 deleted the cst-i163 branch February 17, 2022 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Callback is not registered, when multiple callbacks have the same output

2 participants