Proxy API enhancements
Issue #15
new
András Jankó created an issue 2017-09-15
- Automated build script for Proxy+API exporter
- Currently, doc page for namespaces does not separate visibly proxied and non-proxied types just has a single list. Sub-pages are created for all, creating a big tree with lot of non-proxied nodes, at least they are grey, but still not too good to look at and also unneeded data to send to the client. I think it would be better to just list non-proxied types/sub-namspaces in the page of the namespace in a separate section and not having it in the tree
- Delegates need some special logic: WS can handle any delegate, even if unseen before, so delegates should be marked ok if all occuring types are proxied
- Enums are even simpler, all enums can be translated without proxies (they just translate to base value)
Comments (1)
-
reporter
- Log in to comment
A related issue that needs to be fixed: the old UI.Next documentation details various input-related APIs, which are for the most part missing from the new, generated API reference pages. The details need to be recovered and the pages regenerated.