PHP & Laravel enthusiast | All about Typescript.
Opinions are mine.
Unfortunately, life has other plans this year!
Unfortunately, life has other plans this year!
With all the awesome work you're doing on route inlay hints.
Reckon we could add support for showing the route above controller actions?
Would be really handy for quick skimming.
With all the awesome work you're doing on route inlay hints.
Reckon we could add support for showing the route above controller actions?
Would be really handy for quick skimming.
Do you have plans to add doing vendor:publish as an action?
Would be wicked to be able to do this without switching to the terminal 💡
Do you have plans to add doing vendor:publish as an action?
Would be wicked to be able to do this without switching to the terminal 💡
Check it out and let us know what you think!
github.com/webfox/larav...
Check it out and let us know what you think!
github.com/webfox/larav...
All it would do is open the "Create Form Request" dialog like you do from the Code Generation menu, but would automatically add it to the controller method once you hit "OK".
All it would do is open the "Create Form Request" dialog like you do from the Code Generation menu, but would automatically add it to the controller method once you hit "OK".
Something like this but for @jetbrains.com products
stillat.com/antlers-tool...
Something like this but for @jetbrains.com products
stillat.com/antlers-tool...
Since the latest update I've been getting this a bit.
Is this a known issue or something specific to me? I've reported the issue via the IDE.
Since the latest update I've been getting this a bit.
Is this a known issue or something specific to me? I've reported the issue via the IDE.
Could have been
public fn save(): bool => $this->query->persist();
For all the example value matters.
Could have been
public fn save(): bool => $this->query->persist();
For all the example value matters.
public function getLevels(): array
{
return ['low', 'med', 'high'];
}
could be
public fn getLevels(): array => ['low', 'med', 'high'];
public function getLevels(): array
{
return ['low', 'med', 'high'];
}
could be
public fn getLevels(): array => ['low', 'med', 'high'];
public function getAdditionalPivotColumns(): array {
return [
'level',
];
}
It would act the same as calling `->withPivot(['level'])` when creating the relationship.
public function getAdditionalPivotColumns(): array {
return [
'level',
];
}
It would act the same as calling `->withPivot(['level'])` when creating the relationship.
@github.com Copilot now has Edits in @jetbrains.com products.
Good to see us getting feature parity with @vscode.dev again.
@github.com Copilot now has Edits in @jetbrains.com products.
Good to see us getting feature parity with @vscode.dev again.
For native elements is `ComponentProps<'button'>` always the right way to do it? What about for components that don't export their prop types? When wouldn't `ComponentProps
#typescript #react
For native elements is `ComponentProps<'button'>` always the right way to do it? What about for components that don't export their prop types? When wouldn't `ComponentProps
#typescript #react
Still neat though
Still neat though
It looks much better now :)
It looks much better now :)
developer.chrome.com/docs/web-pla...
developer.chrome.com/docs/web-pla...