Cristian Tăbăcitu

Results 137 issues of Cristian Tăbăcitu

Thanks to the fluent syntax, I think it'll be possible to have a convenience method that adds the InlineCreate operation to the ```relationship``` field, which would have the exact same...

Feature
Priority: SHOULD
non breaking change

# Feature Request ### What's the feature you think Backpack should have? As mentioned in https://github.com/Laravel-Backpack/Base/issues/422, developers might want to just rename a button, for it to say something else....

Priority: SHOULD

In 4.0 the "crud" prefix was removed from route names. But maybe that wasn't such a great idea. It helped differentiate between front-end routes and back-end routes (admin panel). Maybe...

Priority: COULD
triage

Notice all our packages have EVERYTHING inside the src folder. While that made sense at the time, due to little documentation on how to create Laravel packages, it no longer...

Priority: SHOULD
breaking change
refactoring

As mentioned [here on twitter](https://twitter.com/tabacitu/status/1319255896678072323?s=20)... I'm now wondering if we should make the way @lambasoft suggested _the recommended way_ to extend add-ons in the future... So instead of _creating a...

Feature
Priority: COULD
Priority: SHOULD
enhancement

Hey @pxpm , @karandatwani92 , @jcastroa87 - heads-up. I've just: - created a `v7-dev` directory in Docs - created a `v7` branch in CRUD - created a `v3` branch in...

next-version

TODO: - A. 🔴 Remove the need for symlink by saving the files in the public folder (`public/bassets`), GIT IGNORED: - PROS: - Easier to install: No need to create...

Priority: MUST
v7

## The problem Sometimes, the admin cannot identify an entry based on one attribute alone. Some examples: - for an Order, it's not really useful for the admin to see...

triage
Priority: SHOULD
Size: S

This PR brings the following changes to the Show operation: - moves the table that echoes an entity's attributes... to a component we call `Datalist` - adds a new component...

Priority: SHOULD
Size: S

The `next` branch is where we bring together all fixes&features for our next version. This PR is here to document all PRs merged, all breaking changes, all remaining TODOs about...

Priority: MUST
BLOCKED