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

How can we document extensions? #21

Open
justincy opened this issue Oct 7, 2016 · 2 comments
Open

How can we document extensions? #21

justincy opened this issue Oct 7, 2016 · 2 comments

Comments

@justincy
Copy link
Member

justincy commented Oct 7, 2016

Two problems:

  1. Get the extensions of core data types to appear.
  2. Mark when something is an extension and which spec it belongs to.
@justincy
Copy link
Member Author

If we can, it'd be nice to separate classes into namespaces based on core, rs, atom, records. I tried once but adding namespaces causes classes to be listed with {namespace}. as a prefix in the classes dropdown, such as core.Address. I don't like that; it prevent you from finding classes alphabetically. We would have to fork the template to use name instead of longname.

@justincy
Copy link
Member Author

justincy commented Dec 8, 2016

We are seeing extensions of core data types in the docs but we're not seeing methods of new data types from extensions in the docs. See DisplayProperties for an example; it's missing all getters and setters. In Field we see that it's properly picking up inherited methods.

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

No branches or pull requests

1 participant