You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm observing more and more use cases where people don't know how to behave when seeing this:
Error in UseMethod("join_keys<-", x) :
no applicable method for 'join_keys<-' applied to an object of class "c('qenv.error', 'try-error', 'simpleError', 'error', 'condition')"
(or any other method applied on qenv.error class of object)
Usually the only thing they need to do is to print a given object which should have enough information about the error itself. Now I'm thinking if we can do such print automatically and don't ask users to explicitly print it. We can do print right when the error occurs or print on (any) method calls or something else. Please just make sure to make it easily extendable with regard to methods - anti-pattern would be a new methods: join_keys.qenv.error, join_keys<-.qenv.error and so on... That's not very scalable.
Code of Conduct
I agree to follow this project's Code of Conduct.
Contribution Guidelines
I agree to follow this project's Contribution Guidelines.
Security Policy
I agree to follow this project's Security Policy.
The text was updated successfully, but these errors were encountered:
Feature description
I'm observing more and more use cases where people don't know how to behave when seeing this:
(or any other method applied on
qenv.error
class of object)Usually the only thing they need to do is to print a given object which should have enough information about the error itself. Now I'm thinking if we can do such print automatically and don't ask users to explicitly print it. We can do print right when the error occurs or print on (any) method calls or something else. Please just make sure to make it easily extendable with regard to methods - anti-pattern would be a new methods:
join_keys.qenv.error
,join_keys<-.qenv.error
and so on... That's not very scalable.Code of Conduct
Contribution Guidelines
Security Policy
The text was updated successfully, but these errors were encountered: