Skip to content
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

No means of flagging APIs as "non-pseudo" #102

Open
sgtcoolguy opened this issue Nov 17, 2020 · 0 comments
Open

No means of flagging APIs as "non-pseudo" #102

sgtcoolguy opened this issue Nov 17, 2020 · 0 comments

Comments

@sgtcoolguy
Copy link
Contributor

We should introduce an optional property on types so we can manually classify them as one of our known pseudo types:

  • proxy
  • module
  • view
  • pseudo

Basically we assume anything extending from Ti.Module (or in Global namespace) is a 'module', anything extending from 'Ti.proxy' is a 'proxy', anything extending 'Ti.UI.View' is a 'view' and all others are 'pseudo'.

But when trying to document Node.js shims, they're all getting marked as 'pseudo' (which ends up with the info box saying they're an abstract type).

I assume TypeScript has some nomenclature for declaring types as "abstract/pseudo" versus "normal"? I'd like to flag the top-level node.js shims and 'module's, and any classes they expose as non-abstract types (though they're not really proxies?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant