feat: add block option drop down

[Anushka-Bhowmick]

Fixes #474

My PR closes #474

👨‍💻 Changes proposed(added an onClick code snippet to enhance the code

✔️ Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• This PR does not contain plagiarized content.
• The title and description of the PR is clear and explains the approach.

Note to reviewers

📷 Screenshots

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @Dun-sin on Vercel.

@Dun-sin first needs to authorize it.

[github-actions]

PR Compliance Checks Passed!

[Dun-sin]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

Conventional Commit PR Title

In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass. Most often, our PR titles are something like one of these:

* docs: correct typo in README

* feat: implement dark mode"

* fix: correct remove button behavior

Linting Errors

* Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"

* No subject found

@Anushka-Bhowmick
Please fix this error, if you don't know how, try this:

• Read the error carefully or read the contributing file
• Checkout past merged Pull requests to see how they were done for it to be merged

Note: you can edit your PR message, this PR won't be merged if the error isn't gone and you have a week max to fix it before the PR gets closed without being merged

[Dun-sin]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

Conventional Commit PR Title

In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass. Most often, our PR titles are something like one of these:

* docs: correct typo in README

* feat: implement dark mode"

* fix: correct remove button behavior

Linting Errors

* Found type "enhancement", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"

@Anushka-Bhowmick still there, you know what to do already

[Dun-sin]

wrong again, after quote reply means after the dropdown.item for quote reply, when you make a change like this, ask yourself, does this make sense? You know the answer is no

[Dun-sin]

You did great, thanks for contributing, I hope you will stick around and continue to contribute to this project.

Consider giving this project a star and joining the community discord server if you haven't for more resources and opportunities to connect with others. 👉🏽here👈🏽

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
whisper	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2023 10:47am

[Anushka-Bhowmick]

Thank you! Learned quite some stuffs :)