`hasPopin` does not exist on type `Table`
See original GitHub issueAre only the public methods exposed? sap.m.Table
has a method called hasPopin
:
but the typedefs throw an error:
My version is 1.96, the latest LTM
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Angular - How to fix 'property does not exist on type' error?
It usually happens when you develop Angular applications. To solve this just shut down the server & start it again: $ ng serve....
Read more >(TypeScript) Type definitions are incomplete for sortable tables.
Some type definitions are incomplete -- in the column for example. Property 'getSortByToggleProps' does not exist on type ...
Read more >TS2339 error, Typescript — DataTables forums
I have this error : TS2339: Property 'DataTable' does not exist on type 'JQuery' , Anyone know, how can I fix this error!...
Read more >java.lang.Double cannot be cast to java.lang.String - IssueHint
Double cannot be cast to java.lang. ... You cannot assign double to a String. ... `hasPopin` does not exist on type `Table`, 5,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Well, the generator exposes
@public
and@protected
methods the same way.Therefore, your finding puzzled me a while, until I noticed that the 1st screenshot does not show a JSDoc comment, only a simple block comment which is not evaluated as documentation.
This looks quite unintentional and I’ll let the developers of the
sap.m.Table
control know.Answer from the Table colleagues: those methods are only meant for internal use between related controls. They are planned to be marked as @ui5-restricted, which means they will continue not to be visible in the SDK API documentation and continue not to be meant for use in e.g. applications. So I’m closing this issue.
The topic how “internal” usages of restricted APIs with TypeScript can be supported is generally an open question. Some APIs are restricted to related controls, others to specific stakeholders (which can be informed in case of breaking changes) etc. Of course they need the types defined to easily use them, but on the other hand we cannot produce tailored type definitions for each different group of such internal users. Right now a way out is to define the needed types on top on side of the users.