feat: Add translatable components support #99
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new method to the
AppServiceProviderto automatically enable label translation for several Filament UI components. The goal is to ensure that labels for fields, filters, placeholders, columns, and entries are translated consistently throughout the application.Enhancements for translatable UI components:
translatableComponentsmethod toAppServiceProviderthat configures Filament components (Field,BaseFilter,Placeholder,Column,Entry) to automatically translate their labels by callingtranslateLabel()during configuration.translatableComponentsmethod in thebootlifecycle of the service provider to ensure the translation logic is applied at application startup.Dependency and import updates:
usestatements for Filament component classes and traits at the top ofAppServiceProvider.phpto support the new translation configuration.