Relations are broken in Applications
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Steps to reproduce
- Create a table "Shopping Cart"
- Create a table "Product" which has a relation column to "Shopping Cart"
- Create an application showing both "Shopping Cart" and "Product"
Expected behavior
The relation colums can be edited and viewed like in the normal table view.
Actual behavior
(tables are different from the example above, Product is referencing Procurement here)
The shown error is that the reference entry does not exist, but it does:
The second screenshot is from the table directly.
Tables app version
2.3.0
Browser
No response
Client operating system
No response
Operating system
No response
Web server
No response
PHP engine version
No response
Database
No response
Additional info
Installed based on the manual deploy of the AIO.
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 in the Applications view using two tables with a relation column, then compare its behavior with the normal table view described in the report. Trace the application’s relation handling from the failing view; done means relation columns can be viewed and edited without reporting that an existing reference entry is missing.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100