Fix ESlint

.eslintrc.json

@@ -18,6 +18,7 @@
     "react/jsx-props-no-spreading": "off",
     "no-underscore-dangle": "off",
     "no-param-reassign": "off",
-    "no-console": "off"
+    "no-console": "off",
+    "class-methods-use-this": "off"
   }
 }

.github/dependabot.yml

@@ -1,9 +1,9 @@
 version: 2
 updates:
-  - package-ecosystem: "npm" # See documentation for possible values
-    directory: "/" # Location of package manifests
+  - package-ecosystem: 'npm' # See documentation for possible values
+    directory: '/' # Location of package manifests
     schedule:
-      interval: "daily"
+      interval: 'daily'
     ignore:
-      - dependency-name: "react-dnd"
-      - dependency-name: "react-dnd-html5-backend"
+      - dependency-name: 'react-dnd'
+      - dependency-name: 'react-dnd-html5-backend'

CODE_OF_CONDUCT.md

@@ -20,28 +20,28 @@ If you see someone who is making an extra effort to ensure our community is welc
 
 The following behaviors are expected and requested of all community members:
 
- * Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
- * Exercise consideration and respect in your speech and actions.
- * Attempt collaboration before conflict.
- * Refrain from demeaning, discriminatory, or harassing behavior and speech.
- * Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
- * Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+- Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+- Exercise consideration and respect in your speech and actions.
+- Attempt collaboration before conflict.
+- Refrain from demeaning, discriminatory, or harassing behavior and speech.
+- Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+- Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
 
 ## 4. Unacceptable Behavior
 
 The following behaviors are considered harassment and are unacceptable within our community:
 
- * Violence, threats of violence or violent language directed against another person.
- * Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
- * Posting or displaying sexually explicit or violent material.
- * Posting or threatening to post other people's personally identifying information ("doxing").
- * Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
- * Inappropriate photography or recording.
- * Inappropriate physical contact. You should have someone's consent before touching them.
- * Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
- * Deliberate intimidation, stalking or following (online or in person).
- * Advocating for, or encouraging, any of the above behavior.
- * Sustained disruption of community events, including talks and presentations.
+- Violence, threats of violence or violent language directed against another person.
+- Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+- Posting or displaying sexually explicit or violent material.
+- Posting or threatening to post other people's personally identifying information ("doxing").
+- Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+- Inappropriate photography or recording.
+- Inappropriate physical contact. You should have someone's consent before touching them.
+- Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+- Deliberate intimidation, stalking or following (online or in person).
+- Advocating for, or encouraging, any of the above behavior.
+- Sustained disruption of community events, including talks and presentations.
 
 ## 5. Weapons Policy
 
@@ -59,15 +59,11 @@ If a community member engages in unacceptable behavior, the community organizers
 
 If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. React Big Schedule Team.
 
-
-
 Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
 
 ## 8. Addressing Grievances
 
-If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify react-scheduler with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies. 
-
-
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify react-scheduler with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
 
 ## 9. Scope
 
@@ -81,7 +77,7 @@ React Big Schedule Team
 
 ## 11. License and attribution
 
-The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/). 
+The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).
 
 Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
 

CONTRIBUTING.md

@@ -1,40 +1,55 @@
 # Contributing Guide for react-big-schedule
+
 Welcome to the react-big-schedule project! We're thrilled that you're interested in contributing to our open-source scheduling component for React. By contributing to this project, you can help make it even better and support the broader developer community.
+
 ### Code of Conduct
+
 Before you start contributing, please take a moment to read our Code of Conduct. We expect all contributors to adhere to these guidelines to ensure a positive and inclusive community for everyone. You can find our Code of Conduct [here](https://github.com/react-scheduler/react-big-schedule/blob/master/CODE_OF_CONDUCT.md).
+
 ### Getting Started
+
 If you're new to the project, it's a good idea to familiarize yourself with the [README.md](https://github.com/react-scheduler/react-big-schedule/blob/master/README.md) file, which provides an overview of the project and its features. Also, explore existing issues and pull requests to understand the ongoing work and discussions.
+
 ### How to Contribute
+
 We value contributions in various forms – from reporting issues and suggesting improvements to submitting feature requests and providing code changes. To get started with your contributions, follow these steps:
+
 1. #### Fork the Repository
-    Begin by forking the main repository to your GitHub account. This will create a personal copy of the project that you can work on.
+   Begin by forking the main repository to your GitHub account. This will create a personal copy of the project that you can work on.
 2. #### Set up the Development Environment
-     Clone the forked repository to your local machine and set up the development environment using the instructions provided in the [README.md](https://github.com/react-scheduler/react-big-schedule/blob/master/README.md) file.
+   Clone the forked repository to your local machine and set up the development environment using the instructions provided in the [README.md](https://github.com/react-scheduler/react-big-schedule/blob/master/README.md) file.
 3. #### Create a Branch
-      Create a new branch for your specific contribution. Please use a descriptive and meaningful name for your branch, such as `fix/issue-123` or `feature/new-feature`.
+   Create a new branch for your specific contribution. Please use a descriptive and meaningful name for your branch, such as `fix/issue-123` or `feature/new-feature`.
 4. #### Make Changes
-      Now comes the coding part! Make the necessary changes to the codebase following the coding guidelines outlined below:
+
+   Now comes the coding part! Make the necessary changes to the codebase following the coding guidelines outlined below:
 
    ##### Coding Guidelines
+
    - Follow the JavaScript Standard Style, as it helps maintain a consistent and readable codebase.
    - Write clear and concise code with meaningful variable and function names.
    - Include appropriate comments to explain complex logic or important details.
    - Run the tests and ensure they pass before submitting the changes.
+
 5. #### Testing
-      For bug fixes, add new test cases that demonstrate the fixed behavior. For new features, include comprehensive test coverage to maintain a high level of code quality. Run the test suite locally to confirm that all tests pass successfully.
+   For bug fixes, add new test cases that demonstrate the fixed behavior. For new features, include comprehensive test coverage to maintain a high level of code quality. Run the test suite locally to confirm that all tests pass successfully.
 6. #### Commit and Push
-     Commit your changes with a descriptive and concise commit message. Once you are satisfied with your changes, push the branch to your forked repository.
+   Commit your changes with a descriptive and concise commit message. Once you are satisfied with your changes, push the branch to your forked repository.
 7. #### Create a Pull Request
-    Go to the original repository and create a Pull Request (PR). Fill in the PR template with relevant information, including a clear description of your changes and the problem they address. A maintainer will review your PR, and there may be some feedback or adjustments required before it gets merged.
+   Go to the original repository and create a Pull Request (PR). Fill in the PR template with relevant information, including a clear description of your changes and the problem they address. A maintainer will review your PR, and there may be some feedback or adjustments required before it gets merged.
 8. #### Collaboration and Feedback
-     Our maintainers and community members will review your contributions and provide feedback. Be open to suggestions and actively participate in discussions to improve your work.
-10. #### Celebrate
-      Congratulations on your contribution! Your efforts help improve this project for everyone. Once your PR gets merged, your contribution will be acknowledged in the project's release notes and contributors' list.
+   Our maintainers and community members will review your contributions and provide feedback. Be open to suggestions and actively participate in discussions to improve your work.
+9. #### Celebrate
+   Congratulations on your contribution! Your efforts help improve this project for everyone. Once your PR gets merged, your contribution will be acknowledged in the project's release notes and contributors' list.
 
 ### Reporting Issues
-  If you encounter a bug, have a feature request, or need assistance with the library, please open an issue on the GitHub repository. Use the issue template to provide necessary details to help us understand the problem better.
+
+If you encounter a bug, have a feature request, or need assistance with the library, please open an issue on the GitHub repository. Use the issue template to provide necessary details to help us understand the problem better.
+
 ### Acknowledgment
-  Thank you for taking the time to contribute to react-big-schedule! Your passion and effort are what make open-source communities thrive. We value your contributions and look forward to seeing you grow with the project.
+
+Thank you for taking the time to contribute to react-big-schedule! Your passion and effort are what make open-source communities thrive. We value your contributions and look forward to seeing you grow with the project.
+
 #### Happy coding!
 
-- The react-big-schedule Team 
+- The react-big-schedule Team