Skip to content

Styling: Moved the pulsing beacon animation to styling for reuse#4446

Merged
lynamemi merged 2 commits intomicrosoft:masterfrom
lynamemi:add-beacon-styling
Apr 4, 2018
Merged

Styling: Moved the pulsing beacon animation to styling for reuse#4446
lynamemi merged 2 commits intomicrosoft:masterfrom
lynamemi:add-beacon-styling

Conversation

@lynamemi
Copy link
Copy Markdown
Collaborator

@lynamemi lynamemi commented Apr 3, 2018

Pull request checklist

  • Addresses an existing issue: Fixes #0000
  • Include a change request file using $ npm run change

Description of changes

Moved the pulsingBeacon animation from Coachmark into its own file in the Styling package. Let me know if it makes more sense to you to put it somewhere else.

I will be reusing this animation for ActivityItem. The design and behavior has not changed.

Focus areas to test

(optional)

@lynamemi
Copy link
Copy Markdown
Collaborator Author

lynamemi commented Apr 4, 2018

@phkuo Sorry had to split up that other PR you approved yesterday - this is the same code for Styling, but without the changes to Coachmark. That will be a separate PR.

const DEFAULT_DELAY = '2s';
const DEFAULT_ITERATION_COUNT = '1';

function _continuousPulseStepOne(beaconColorOne: string, innerDimension: string): IRawStyle {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm pretty sure you can have numbers in function names, it just can't start with a number.

@lynamemi lynamemi merged commit 93fdd29 into microsoft:master Apr 4, 2018
@lynamemi lynamemi deleted the add-beacon-styling branch April 4, 2018 22:41
@microsoft microsoft locked as resolved and limited conversation to collaborators Aug 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants