feat: add relation column type

[Koc]

This PR introduces a basic relation type. It allows to connect few tables together. We will store row id as a column value and display selected column as a label for this values. Closes #172.

✔️ Implemented

🔍 Column create/edit

🔍 Row create/edit via popup/inline

🔍 Row display in table/view + handle relation row removal

🔍 Filter for view

🔍 Filter for rows

🔍 Import/Export

🚧 Pending (help welcomed):

• Behat tests
• Cypress tests?

❎ What is out of scope:

• Lookup columns to add an extra columns from the related table to the current one. It will be handled separately in upcoming PR.

[enjeck]

would be nice to have tests to avoid regressions in the future

[Koc]

@Aveyron-RetD here we go, without tooltip

[Koc]

hey @enjeck @blizzz!

I've added Behat tests, please check. Is that enough to merge PR?

[enjeck]

Thank you so much!

[xbluemonkx]

H,
I have seen that this is part of the new release. - May I ask what exactly this offers now?

Is it possible to define "link" columns (columns that are avaible in to tables so if someone adds and entry in table A it is possible to use it in table B as a link?

Or is it more like: if i manually enter the same value in table A and table B it can be used as a link?

I am really curious about what / how this actually works from a user perspective

[Koc]

@xbluemonkx mate, sorry, but I didn't got what you mean. You can check screenshots from the PR description or even checkout latest version of the module, install it locally and test by yourself (and answer to your question 😉)

[Aveyron-RetD]

@xbluemonkx i believe this is this feature #2271 ,that you want which will bring you lookup columns.
In this feature, there is only text field which works.

What you can do for the moment with this feature is for example an ordering table from an inventory table. You can have a table with all your references (A) and another table where you can order (B) when you create a relation column in table (B) you reference to a text field column in table A for example (Inventory name).

So by editing table A, you create new references, and they will appear as selection choices in table B.
The only downside they could be restricting your searches because the text field could be not enough for the user to recognize the inventory and this is where #2271 will come handy. It will fetch other results in table A on the same row and prefill cells depending on the text field chosen.

Am i right @Koc ?

[Koc]

yeah, you are pretty good explained how it works, thanx!