epam/miew

_(Please do not forget to update the PR title using imperative mood as with commit messages; and delete this line, of course)_

## Description

_(Refer to the corresponding issue # here if any. Otherwise, provide motivation and context: why this change is required? what problem does it solve?)_

_(Provide a clear and concise description of what the changes are)_

_(Please [add screenshots](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests/) if appropriate)_

## Type of changes
_(Leave only items that apply)_

- 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 not work as expected)

## Checklist
_(Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code)_

- [ ] I have read [CONTRIBUTING](https://github.com/epam/miew/blob/master/CONTRIBUTING.md) and [CODE_OF_CONDUCT](https://github.com/epam/miew/blob/master/CODE_OF_CONDUCT.md) guides.
- [ ] I have followed the code style of this project.
- [ ] I have run `yarn run ci`: lint and tests pass locally with my changes.
- [ ] I have added tests that prove my fix is effective or that my feature works.
- [ ] I have added necessary documentation / The changes do not need docs update.