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

docs: added note in animation keyframe offset #32350

Closed
wants to merge 1 commit into from

Conversation

jrumandal
Copy link
Contributor

@jrumandal jrumandal commented Aug 27, 2019

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Not mentioned in the docs.
Whenever offset property is used inside a keyframe's step at least once, then it must be defined to all the steps.
When read the first time, I supposed that the API automatically sets an even offset to the remaining not defined offsets, which is not
Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@jrumandal jrumandal requested a review from a team as a code owner August 27, 2019 16:36
@ngbot ngbot bot added this to the needsTriage milestone Aug 27, 2019
@ngbot ngbot bot modified the milestones: needsTriage, Backlog Aug 28, 2019
@kapunahelewong kapunahelewong added the target: patch This PR is targeted for the next patch release label Aug 28, 2019
@kapunahelewong kapunahelewong added this to In Review in docs Aug 29, 2019
Copy link
Contributor

@kapunahelewong kapunahelewong left a comment

Choose a reason for hiding this comment

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

Just one little note. Thanks, @jrumandal!

aio/content/guide/transition-and-triggers.md Outdated Show resolved Hide resolved
@jrumandal
Copy link
Contributor Author

@kapunahelewong Somehow the pipeline does not like it. Any suggestion?

@kapunahelewong
Copy link
Contributor

Hm, a rebase might help. Here are my steps to rebase if you'd like them for reference. Rebasing will hopefully fix those. Will you tag me when you've rebased? If the rebase goes ok and they still fail, at least we'll know we're on the latest and can work from there.

@googlebot
Copy link

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: yes and removed cla: no labels Sep 3, 2019
@jrumandal
Copy link
Contributor Author

Hm, a rebase might help. Here are my steps to rebase if you'd like them for reference. Rebasing will hopefully fix those. Will you tag me when you've rebased? If the rebase goes ok and they still fail, at least we'll know we're on the latest and can work from there.

@kapunahelewong It should be good now, thanks for guidelines. I'll treasure it for the future :)

@kapunahelewong
Copy link
Contributor

So glad it worked, @jrumandal 😊

Everything looks good, but we need just one commit in the PR (at the moment, there are two). Could you squash? Here's my workflow for squashing. We're almost there! 🛵

Not mentioned in the docs.
Whenever offset property is used inside a keyframe's step at least once, then it must be defined to all the steps.
When read the first time, I supposed that the API automatically sets an even offset to the remaining not defined offsets, which is not
@jrumandal
Copy link
Contributor Author

So glad it worked, @jrumandal 😊

Everything looks good, but we need just one commit in the PR (at the moment, there are two). Could you squash? Here's my workflow for squashing. We're almost there! 🛵

@kapunahelewong Got it! :)

Copy link
Contributor

@kapunahelewong kapunahelewong left a comment

Choose a reason for hiding this comment

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

Thank you so much, @jrumandal!

@kapunahelewong
Copy link
Contributor

Caretaker, this is a docs only change. Thank you!

@kapunahelewong kapunahelewong added the action: merge The PR is ready for merge by the caretaker label Sep 5, 2019
@matsko matsko closed this in cc06153 Sep 5, 2019
matsko pushed a commit that referenced this pull request Sep 5, 2019
Not mentioned in the docs.
Whenever offset property is used inside a keyframe's step at least once, then it must be defined to all the steps.
When read the first time, I supposed that the API automatically sets an even offset to the remaining not defined offsets, which is not

PR Close #32350
sabeersulaiman pushed a commit to sabeersulaiman/angular that referenced this pull request Sep 6, 2019
Not mentioned in the docs.
Whenever offset property is used inside a keyframe's step at least once, then it must be defined to all the steps.
When read the first time, I supposed that the API automatically sets an even offset to the remaining not defined offsets, which is not

PR Close angular#32350
@kapunahelewong kapunahelewong moved this from In Review to Waiting for Approval in docs Sep 16, 2019
@kapunahelewong kapunahelewong moved this from Waiting for Approval to Done in docs Sep 16, 2019
arnehoek pushed a commit to arnehoek/angular that referenced this pull request Sep 26, 2019
Not mentioned in the docs.
Whenever offset property is used inside a keyframe's step at least once, then it must be defined to all the steps.
When read the first time, I supposed that the API automatically sets an even offset to the remaining not defined offsets, which is not

PR Close angular#32350
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes effort1: hours risk: low target: patch This PR is targeted for the next patch release type: bug/fix
Projects
docs
Done
Development

Successfully merging this pull request may close these issues.

None yet

5 participants