Liam Hammett

Didn't even realise it uses `` there for the human-readable format, the docs also show `` for its example currently. But yes, that's exactly what I mean in that they...

@pktharindu FYI I absolutely prefer using keys in a real application that needs full translations, especially combined with a tool like [i18n-ally](https://marketplace.visualstudio.com/items?itemName=antfu.i18n-ally) to see the real values inline with code...

> However is it a possibility to add both as a option? As far as I know the `php artisan ui` does support options. @Wulfheart I'm not sure how we...

I'd prefer it the other way around myself (the full strings by default because it's easier for people to understand, swapping out to the keys for people that actually want...

> Please merge this, it just adds i18n in the exact same way as the Tailwind preset and the default Laravel preset already do. There's been a discussion in #12...

One thing we're generally trying not to do in this preset is to maintain multiple files that do the same thing, as you can see by the discussion in #12...

@AlexMartinFR do you happen to know what happened with that experiment to convert PHPUnit tests to Pest and if it's a viable thing to use here?

I've made a start in #31 that, right now, just has an application layout shell. If people are okay with that as it is, we can merge it and add...

Choosing a custom `username` is as simple as editing the `email` fields there, just as you'd override the `username()` method in the default `LoginController` - I don't think that concern...

I've just released an extension that does the same: https://github.com/imliam/vscode-inline-parameters It was originally just for PHP, but since I saw this was no longer maintained I also pulled in the...