Repository navigation
Fix: discussions page crash (MAX_CATEGORY_CHIPS is not defined) - #2372
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Thank you for submitting your pull request! 🙌 We'll review it asap. The estimated time for response is 5–8 hrs. In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, if it's a Video -LEGEND, which helps speed up the review. If you have questions, reach out to LinkedIn. You can see in our Leaderboard in 20 min from now!😊 Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv. We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰 🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨ 📚Your perks for contribution to this community 👇🏻
Thanks again for your contribution! 😊 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
✅ Synchronized metadata from Issue #2368:
|
|
🎉 Your pull request has been successfully merged! 🎉 Thank you for your valuable contribution to our project. I would be grateful if you can nominate for keeping this opensource project live and running Link to Nominate. Please do star the repo and Keep up the fantastic work! 🚀 |
The category chip limit from #2368 used a constant that was never defined, so the Discussions tab crashed with "MAX_CATEGORY_CHIPS is not defined". This defines it. Built and loaded in a headless browser: the page renders 23 posts and five chips (All, Announcements, Ideas, Q&A, General), no crash.