-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ManagedObject: properties awaiting function should have type: "function"
instead of type: "any"
#1908
Comments
Hello @boghyon , Thank you for sharing this finding. I've created an internal incident 1870103964 and the colleagues will comment here in GitHub if the change is possible. Regards, |
I considered to adapt those controls when I introduced the type That doesn't mean it can't be done, but we have to leave the decision up to the control owners. |
Hi, I checked the respective controls as (co-)owner/author of involved code in Dialog, MessageView and MessagePopover. The discussed change should have already be done - we were just not aware of the new API. Type 'any' is there for historical reasons and used only because of no better alternative at the time of implementation. Best regards, |
type: "function"
instead of type: "any"
Since 7f32a36 & 860805d, it is possible to define
"function"
as a type of property. However, many modules, derived from ManagedObject, still use the type"any"
whereas a function is awaited.It would be nice if they adapt to the "new" type so that at least the API Reference can display the type correctly.
URL (minimal example if possible):
escapeHandler
--> Fixed by 16fad20asyncDescriptionHandler
asyncURLHandler
asyncDescriptionHandler
asyncURLHandler
textFormatter
suggestionRowValidator
groupHeaderFormatter
--> Fixed by 219630c... Probably more (didn't check closed sourced modules)
What is the expected result?
type: "function"
if applicable.What happens instead?
type: "any"
The text was updated successfully, but these errors were encountered: