🛠️FIX : Uncaught Runtime Error Prevents Local Development

[akash70629]

Description

After forking and cloning the repository, I encountered a major issue while setting up the local environment. Upon running npm install and npm start, I received an uncaught runtime error.

To resolve this, you can modify your code to handle the case where the stored theme is a simple string instead of a JSON string. Here's how you can do that:

Retrieving the theme: Instead of using JSON.parse, you directly retrieve the item from local storage. Checking for storedTheme: If storedTheme is not null (meaning there is a value stored), it will return that value directly, which should be either "dark" or "light". Fallback: If there’s no stored theme, it defaults to checking the document's class to determine the current theme. This approach avoids any JSON parsing issues and should fix the "Unexpected token 'd'" error.

I fixed that.

Related Issues

Fixes : #489

Changes Proposed

Changed some line of code on Sidebar.jsx

Checklist

• [x] I have read and followed the Contribution Guidelines.
• [x] All new and existing tests passed.
• [x] I have updated the documentation to reflect the changes I've made.
• [x] My code follows the code style of this project.
• [x] The title of my pull request is a short description of the requested changes.

Screenshots

Before

https://github.com/user-attachments/assets/76dc452d-09d0-4295-8cc0-a0735a92ce35

After

https://github.com/user-attachments/assets/87326385-d650-40af-86f1-1ea40e7a39dd

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
devdisplay	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 18, 2024 3:03pm

[akash70629]

@madhukalita please review and merge the PR .