-
Notifications
You must be signed in to change notification settings - Fork 34
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
Introduce Tabs #14
Comments
+1 for this. Especially valuable for models that have many relationships defined, as those detail pages can get lengthy. Personally, I'd like to see tabs at the page level instead of (or in addition to) panel tabs. Any fields outside a
|
+1 as well for tabs. Sometimes, there are multiple levels of nested resources (5+, 10+) and you just need to be able to quickly drill into the related resources via a link vs displaying them on the parent. This is when a breadcrumb-type nav component would help as well. This should be great to have as any option on the HasMany, etc.-type relationship fields. Similarly, it would be great to be able to define a right-sidebar/panel where certains Actions, Report links, or Even cards could live. Love Nova so far and can't wait to see where it goes from here! |
+1 to this. When you have a bunch of relations in a model easily becomes infinite. |
+1 |
We just published a basic tab package in case anyone's interested: |
FYI - When using nova-tabs as a replacement for panels it breaks the HasMany field, causing it to return every row in the database instead of the related rows. Reverting back to the Nova supplied field panel restores the expected behavior. I've created an issue for on the nova-tabs repo. |
Also, updating date's is not working. |
I would like to add another case for Tabs. Tabs can also be used for listing rows with predefined filters. Something similar to the screenshot below. I was thinking of using a method to create tabs with predefined filter view /**
* Get the tabs available for the resource.
*
* @param \Illuminate\Http\Request $request
* @return array
*/
public function tabs(Request $request)
{
return [];
} |
@johannitsa In https://github.com/dkulyk/nova-tabs you can use Tabs like @dwyer14 says. public function fields(Request $request)
{
return [
ID::make()->sortable(),
new Tabs('Information', [
new Panel('Personal Information', $this->personalFields(),
new Panel('Progress', $this->progressFields()),
BelongsToMany::make('Relations'),
]),
];
}``` |
@dkulyk Yo, that is slick as h*ck. Nice work! Would love to see something like that in the core. |
I think this should get some attention, right @davidhemphill ?:) |
Hey there! In order to keep this repository focused on bug reports, we auto-close feature requests and requests for help. Feel free to post your feature requests so others can discuss and add reactions. We'll keep an eye on them for later planning. |
Packages providing tabs for Nova: |
I have reached so many dead ends because "this repository is focused on bugs". And this specific one is also saying to post feature requests as well? |
Most of the ones from the last year or so have the same message above. 😄 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hey,
Nova is a great product!
I was thinking that we can do something better to group fields.
We can use the same idea to group/navigate through relationships.
I believe that this may improve the UX.
Regards!
The text was updated successfully, but these errors were encountered: