Skip to content

Conversation

@helen-v
Copy link

@helen-v helen-v commented Mar 15, 2021

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

(Bug fix, feature, docs update, ...)

[Type here]

What is the current behavior?

(You can link to an open issue)

[Type here]

What is the new behavior

(if this is a feature change)?

[Type here]

Does this PR introduce a breaking change?

(What changes might users need to make in their application due to this PR?)

[Type here]

Other information:

[Type here]

@yananym
Copy link
Collaborator

yananym commented Mar 17, 2021

The base of the widget itself need to be a trigger button. While the notes are pleased in menu overlay

@helen-v
Copy link
Author

helen-v commented Mar 17, 2021

The base of the widget itself need to be a trigger button. While the notes are pleased in menu overlay

Done

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