projects feature raising a Visible fields must be fewer than 1351 bytes as JSON

[galloramiro]

Select Topic Area

Bug

Feature Area

Projects

Body

Description

Im trying to save a view on my public projects, but i'm getting a 422 with a Visible fields must be fewer than 1351 bytes as JSON.

This is an expected behavior? I didn't find any documentation on it.

I did found this, but not sure if they are completely related:

• https://github.com/orgs/community/discussions/154313
• https://github.com/orgs/community/discussions/152407

How to reproduce the issue

1. Enter jrnl-habits-tracker roadmap
2. Modify any filter on the view options
3. Try to save the view
4. Get the error

Images

Thanks!

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[rileybroughten]

This has been resolved. Please let us know if you encounter this issue again! Thank you!

[galloramiro]

Fixed, thanks!