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
Traceback (most recent call last):
...
ValueError: No method was found starting with 'someMethod' and with keywords {'invalidArg'}
Known keywords are:
frozenset({''})
frozenset({'', 'validArg'})
This will be as follows after #453 is resolved because frozenset will be changed to tuple:
ValueError: No method was found starting with 'someMethod' and with keywords ('invalidArg')
Known keywords are:
('')
('', 'validArg')
Describe the solution you'd like
I think the converted selector name and available selector names should be shown.
ValueError: Invalid selector 'someMethod:invalidArg:'. Available selectors are: 'someMethod:', 'someMethod:validArg:'
Describe alternatives you've considered
It is also possible to show descriptions of Python, not selectors.
Agreed this would be a good improvement - especially if it were paired with an implementation of #453 and #148.
Of the two syntax options you've presented, I'd lean towards the "selector" description - any user is trying to invoke an ObjC method, so I don't think we gain anything by trying to avoid ObjC syntax in error messages.
What is the problem or limitation you are having?
The current error message is as follows:
This will be as follows after #453 is resolved because
frozenset
will be changed totuple
:Describe the solution you'd like
I think the converted selector name and available selector names should be shown.
Describe alternatives you've considered
It is also possible to show descriptions of Python, not selectors.
Actual values of arguments are represented as
...
.Additional context
No response
The text was updated successfully, but these errors were encountered: