Mandatory state of a richtext column in view not persisted
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Steps to reproduce
- Create a table and add a mandatory richtext column
- Create a view and save
- Try to edit the row or
- Open the "Edit View" modal
Expected behavior
The column should be mandatory in the view by default.
Actual behavior
- After creating the view → edit row → the column does not appear as mandatory anymore.
- The same goes for when you open the "Edit View" modal → the column does not appear as mandatory anymore (although it has the mandatory-indicator aka red *)
Tables app version
No response
Browser
Brave
Client operating system
No response
Operating system
No response
Web server
None
PHP engine version
None
Database
None
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by creating a table with a mandatory richtext column, saving a view, then checking both row editing and the Edit View modal. Start by tracing how the view saves and reloads column mandatory state, and compare that state with the red mandatory indicator. Done means the column remains mandatory in both places after the view is saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100