We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
3.1.27
3.2.15
8.2.8
It seems that the recent update in #277 causes an error with custom blocks.
Loading custom blocks in something like an edit page now throws an error like Undefined array key "text_input". text_input being our custom block.
Undefined array key "text_input"
text_input
Changing the code changed in #277 manually fixes the issue.
Custom blocks should able to be loaded in the edit page with the TipTapEditor
Implement a custom block like we did in https://github.com/canyongbs/advisingapp/blob/main/app-modules/form/src/Filament/Blocks/TextInputFormFieldBlock.php
Create a new item with this custom block.
Load it in the TipTapEditor via something like an edit page.
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Filament Version
3.1.27
Plugin Version
3.2.15
PHP Version
8.2.8
Problem description
It seems that the recent update in #277 causes an error with custom blocks.
Loading custom blocks in something like an edit page now throws an error like
Undefined array key "text_input"
.text_input
being our custom block.Changing the code changed in #277 manually fixes the issue.
Expected behavior
Custom blocks should able to be loaded in the edit page with the TipTapEditor
Steps to reproduce
Implement a custom block like we did in https://github.com/canyongbs/advisingapp/blob/main/app-modules/form/src/Filament/Blocks/TextInputFormFieldBlock.php
Create a new item with this custom block.
Load it in the TipTapEditor via something like an edit page.
Reproduction repository
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: