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

Fix translate3d call after transform refactor #1478

Merged
merged 1 commit into from
May 2, 2015

Conversation

dfreedm
Copy link
Member

@dfreedm dfreedm commented May 1, 2015

No description provided.

* @param {number} x X offset.
* @param {number} y Y offset.
* @param {number} z Z offset.
* @param {HTMLElement} node Optional Element to apply the transform to.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For optional arguments, you can call that out via the type expression via a trailing =:

@param {HTMLElement=} node Element to apply the transform to.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should go over the whole codebase. There are plenty of "Optional in description only" type expressions. I'll fix them for this PR, just noting for future reference.

kevinpschaaf added a commit that referenced this pull request May 2, 2015
Fix translate3d call after transform refactor
@kevinpschaaf kevinpschaaf merged commit 0b71b5b into 0.8-preview May 2, 2015
@kevinpschaaf kevinpschaaf deleted the translate3d-refactor branch May 2, 2015 02:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants