search

Laravel-Backpack / community-forum

A workspace to discuss improvement and feature ideas, before they're actually implemented.
28 stars 0 forks source link

[DevTools] CRUD Route and Sidebar Item files to be shown in Files #225

Open Polfo opened 2 years ago

Polfo commented 2 years ago

Bug report

What I did

Create a Model through the devtools interface. Look at files related to a model http://127.0.0.1:8000/admin/devtools/model/281474979084706/related-files

What I expected to happen

Be able to see the Migration, Crud Route and Sidebar Item

What happened

The navigation is grayed out

<a class="nav-link disabled " id="v-pills-migration-tab" data-toggle="pill" data-file="migration" href="#v-pills-migration" role="tab" aria-controls="v-pills-migration" aria-selected="false">Migration</a>

<a class="nav-link disabled " id="v-pills-sidebar_item-tab" data-toggle="pill" data-file="sidebar_item" href="#v-pills-sidebar_item" role="tab" aria-controls="v-pills-sidebar_item" aria-selected="false">Sidebar Item</a>

Backpack, Laravel, PHP, DB version

When I run php artisan backpack:version the output is:

PHP VERSION:

PHP 8.0.2 (cli) (built: Feb 3 2021 18:36:40) ( ZTS Visual C++ 2019 x64 ) Copyright (c) The PHP Group Zend Engine v4.0.2, Copyright (c) Zend Technologies with Zend OPcache v8.0.2, Copyright (c), by Zend Technologies

LARAVEL VERSION:

v8.74.0@004ea195012d5132eca07a176a6e587c6a74815e

BACKPACK VERSION:

4.1.61@4400187391eb5b73672c2b166a990cd737277409

Operating System and Server Setup

I encountered the problem above on my [Windows 10] machine, and my web server is set up using [php artisan serve].

tabacitu commented 2 years ago

Indeed - like everything else that's greyed out and unclickable in DevTools, that's an "upcoming feature", not a bug.

It's interesting that you've found these to be bugs, perhaps it would be best to not show those greyed out "plans" at all. They were helpful to us in determining how to structure the UI (keep the future in mind), but... maybe they're bad for UX. Our thinking is that they would tell the user "here is where this feature will be when it's ready", but maybe that does more harm than good. It may make some users focus on what's NOT ready, instead of on what IS ready.