Thanks for your contribution! For your convenience and to give some guidelines to the one who is going to review your pull request, here's a checklist:

• The pull request has a clear description which summarizes the purpose and the technical changes made.
• Unit tests exist which cover the modified or added code.
• The tests pass.
• The pull request doesn't add duplicate code.
• The pull request follows single responsibility principle for all functions, methods and objects.
• Functions, methods, objects and variables added by this pull request have descriptive names that make it easy and intuitive to understand what they are about.
• Documentation is descriptive.
• The code in this pull request doesn't introduce any security issues. For reference: OWASP top ten vulnerabilities.

Acceptance 👍