Are there any examples of custom language lines for form components

1. Publish and Modify the Translation Files:
- Run the command `php artisan vendor:publish --tag="form-components-translations"` to publish the translation files to your `resources/lang/vendor/form-components` directory.
- Modify the language lines in these files to match your desired translations. For example, you could change the "Submit" translation for the submit button.

php
// resources/lang/vendor/form-components/en/form-components.php
return [
    'submit' => 'Save Changes',
];

2. Use the `__()` Helper:
- You can use the `__()` helper function to localize the labels and other text in the form components.
- For example, you can use `label="__('user.name')"` to localize the label for the "name" field.

html
<x-form-input name="name" label="__('user.name')" />

3. Extend the Component Classes:
- If you need more control over the localization, you can extend the component classes and override the `getLabel()`, `getPlaceholder()`, and other methods that return localized strings.
- This allows you to implement your own localization logic, such as using a different translation package or fetching translations from a database.

php
class CustomFormInput extends \ProtoneMedia\LaravelFormComponents\Components\FormInput
{
    public function getLabel(): ?string
    {
        return __('custom.name_label');
    }
}

4. Customize the Configuration:
- In the published configuration file, you can set the `'translations_path'` option to a custom path where your translation files are located.
- This allows you to use a different directory structure for your translations.

php
// config/form-components.php
return [
    'translations_path' => resource_path('lang/vendor/my-form-components'),
];

By using these customization options, you can ensure that the language lines in the Laravel Form Components library match the rest of your application's localization strategy, providing a consistent user experience across your forms and other parts of the application.