Prevented dependency injection of Models (non existent?)
$record
. For example, you could just do Post $post
instead of Post $record
. Whilst this was convenient, there are quite often situations where you think there should be a record, but there actually is not (e.g. in complex forms with relationships etc). In that case, returning Post $record
would fail on that the argument definition does not allow null, prompting a change to ?Post $record
. However, without the above change you linked, the Post $post
would still return a Post model, but then an empty one that does not exist at all created by Laravel dependency injection. This causes then weird bugs in your code later one if you expect $post
to be the current $record
and it turns out to be just an empty unsaved model. Therefore, if the requested parameter is an Eloquent parameter that is not of the current record/model, this line has been added to prevent such unwanted empty model resolutions.
See also here: https://github.com/filamentphp/filament/pull/15160...RichEditor - TipTap - Custom Block for embedding HTML
data-*
attributes are not rendered. Same thing for <script>
tags
the database has the embedable html just fine. When i dd()
i also get it just fine. The problem appears when i try to render it using {!! $content !!}
Any help is greatly appreciated! Thanks!...has something changed Filament v3.3.37?
File uploads throw a 401
Problem with $getId in filament-schema grid component
How to disable the policy behaviour on the filament resource?
Version 4 File Structure for RelationshipManagers
form
and table
are two not too large functions returning things with complex validations rules and so on, I prefer to keep this components inside the relation manager file. Otherwise, for example, if the table of the relation manager has custom actions, show/hide columns based on a complex logic, etc. I think that it's time to refactor and move to their own files
In addition, you can read about these topics on the Filamanet docs. It doesn't gives you an opinionated answer, it shows you an approach to the "problem" that you are experimenting:
1. Sharing a resource’s form and table with a relation manager....Close open modal from listener on PHP side?
Cannot upload image with TipTap Editor

Why trait for auto generated column is not working?
SQLSTATE[HY000]: General error: 1364 Field 'asset_code' doesn't have a default value
SQLSTATE[HY000]: General error: 1364 Field 'asset_code' doesn't have a default value
Call to a member function makeGetUtility() on null
Running PHP Function From Frontend Click - Component
dispatchFormEvent
but this doesn't seem to exist anymore.Optional modal in an action
\Forms\Components\Select
Empty label not supported anymore for some components

image upload failed

How to test permissions for the Delete action?
Changing a line chart inner circle color

Use same prose style in Filament and front end?