Skip to content

[DOC beta] Enforce public/private declaration for API docs.#11362

Merged
rwjblue merged 1 commit intoemberjs:masterfrom
rwjblue:enforce-documentation-access-specifics
Jun 7, 2015
Merged

[DOC beta] Enforce public/private declaration for API docs.#11362
rwjblue merged 1 commit intoemberjs:masterfrom
rwjblue:enforce-documentation-access-specifics

Conversation

@rwjblue
Copy link
Member

@rwjblue rwjblue commented Jun 7, 2015

This PR ensures that all YUIDoc comment blocks (those starting with /**) are properly marked as either @private or @public.

A number of times throughout the Ember 1.x cycle we have internally struggled with what things are or are not public. This PR "solves" that by making it extremely clear.

In addition to documenting each comment block, a new JSCS rule has been added to ensure all documentation blocks are labeled properly in the future.


Please note: This PR makes an initial attempt based on my best understanding. These @public and @private declarations can absolutely be reviewed and changed as needed.

@rwjblue rwjblue force-pushed the enforce-documentation-access-specifics branch from fc88bd5 to 06d1b0f Compare June 7, 2015 04:18
@DingoEatingFuzz
Copy link
Contributor

Hello @rwjblue, I come to haunt your @private/@public decisions. Namely sortBy being marked private. I came across this in the API and was taken by surprise. We use this a lot in our app and in our tests.

Is there an issue or anything I can be pointed to to read more about the method access decisions?

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

Successfully merging this pull request may close these issues.

2 participants