Make relation documentation clearer

[TobiasPalludan]

I've struggled a little getting started with this framework, especially when it comes to documentation of the relation fields.

In [https://orchid.software/en/docs/field/#relation](the docs), relations are mentioned as standalone, like this.

Relation::make('idea')
    ->fromModel(Idea::class, 'name')
    ->title('Choose your idea');

For me, this will leave an empty relation field that fails silently.
I've since learned that in my projects, I have to do something like this:

Relation::make('user.idea')
    ->fromModel(Idea::class, 'name')
    ->title('Choose your idea');

Since the relation appears on a page belonging to another model.
I don't mind adding a PR with a suggestion for how to reflect this in the docs but wanted to gather feedback beforehand, as I don't have a lot of experience contributing to public repos.

[tabuna]

Hi @TobiasPalludan, I think it depends on the context. To make it clearer, it can be compared as follows.

When writing:

Relation::make('idea')
    ->fromModel(Idea::class, 'name')
    ->title('Choose your idea');

The resulting HTML will be:

<label>Choose your idea</label>

<select name="idea">
    <option value="...">...</option>
</select>

When changing to Relation::make('user.idea'), the resulting HTML will change to <select name="user[idea]">.

They both work fine. However, I usually work with some entity (for example, an Eloquent model) and I want to put as little pressure on it as possible, so I use a prefix that clarifies what it is, for example, "user." and "products.".

It's not necessary to use a prefix. Instead of returning a model with a key in the query method, you can return the model attributes, for example:

public function query(): iterable
{
    return [
        'user' => User::first()
    ];
}

// and usage Input::make('user.name')

or

public function query(): iterable
{
    return User::first()->toArray();
}

// and usage Input::make('name')

I prefer the first method because when you need to modify the screen by adding new entities to it, it will be easy and won't lead to changes in layers. Let me know if you have any questions.