addItemType breaks translations

[ldrshv]

I found a strange bug. FilamentNavigation::addItemType breaks translations of buttons and placeholders on select. If you change Select to TextInput, everything is fine.

[ryangjchandler]

Thanks, I'll investigate this later today.

[kaitwalla]

Having this same issue; interestingly, it also breaks translations elsewhere (for example, on the RichEditor fields in completely separate areas of Filament). Any ideas/ETA on a fix?

I've been beating my head against this for the better part of several hours. Apologies because I'm just trying to get back into Laravel after a while away.

No matter how I change it, whenever the Facade gets called outside the plugin context, that's when translations break. Even calling the exact same code after packageBooted in FilamentNavigationServiceProvider lets everything work. It's only when called outside of that context that the Select field eats it, regardless of what options are used. All other fields I tested worked.

[kaitwalla]

Well, shows what I know. If you register the custom types in AppServiceProvider::boot they work fine.