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

enforce "related" functions order #47

Open
oakmac opened this issue Dec 18, 2014 · 1 comment
Open

enforce "related" functions order #47

oakmac opened this issue Dec 18, 2014 · 1 comment

Comments

@oakmac
Copy link
Member

oakmac commented Dec 18, 2014

The related functions section in the cljsdoc files should always put cljs.core functions first, and then group similar namespace together if they exist.

The cheatsheet tooltips depend on the order being in this way.

I did this manually when I was creating the files, but we should add some code to the Gruntfile to check and make sure this is the case.

@oakmac oakmac self-assigned this Dec 18, 2014
@shaunlebron
Copy link
Contributor

I actually think the order specified in the file should be preserved. When I was writing docs, I would order the related symbols by strength of association.

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

2 participants