-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relationship [Pro] - Not documented how to change attribute showed by pivot select #487
Comments
@realtebo Thanks for pointing out the info we missed. we will add |
That is documented. We just need to maybe link it in more places. |
@pxpm it's not the same we are talking how to change the label showed in the select showed in repeatable field and in the repeatable field managed by the new relationship field. it's not related to saving additional fata |
Yeah ... maybe we need to create a separate section for it. 👍 It's there, but you need to read a bit down: @karandatwani92 will takeover this and make this section more clear in the docs. Thanks for pointing it you @realtebo 🙏 |
@pxpm Yes, i know, but my question is very specific: how can I understand that I can use 'attribute' to change the label of the select ?! Sorry for persisting to point this specific case, but it's so common that I kindly suggest to document [or at least to back-link to a point where ALL of available attributes are documented] sorry, again, but 'if you want change something, change it here' it's not so fun in a documentation page. I hope to not was rude. Sorry, if I was.
|
PR Submited #496 |
We have already changed that bit of the docs to be a full section, and added more examples. I've merged @karandatwani92 suggestion to also add the We will investigate the possibility of creating a page similar to laravel helper methods list where we list all "Field and Column attributes". We could create some kind of a list under each field/column docs with links to those attributes docs. Not sure if it wouldn't bloat the docs toooo much if we name every attribute for every field type. so we may need to "group" them by some kind of categories. Alternatively we could move the docs 1 field/column per page, and in that case we think it's fine if we have a table with all supported attributes at the end. I will open a separate issue for that. Thanks for the suggestion and thanks for the PR @karandatwani92 Cheers |
Starts here: https://backpackforlaravel.com/docs/6.x/crud-fields#relationship-pro
The first [and only, often] info we need here is that if you specificy
attribute
you can switch from a select ofid
s to a select using some label of your choiceThe text was updated successfully, but these errors were encountered: