archtechx / airwire Goto Github PK

Make sure it works & document it

Hi there!

When I stumbled across Airwire, my developer-heart made a little jump of joy. This seems to be the library I've been thinking of so many times... Inertia.js seems to be too much, Livewire 'forces' me to use alpine (I know this aint completely true, but nevermind), but this library just does the wiring, and it lets me be in control of my js side and backend side. Awesome!

My current api-like controllers which can be seen as the soon-deprecated-pre-airwire-component-classes, always handle some business-like validation, and auth related validation. When something goes wrong on that endpoint, I return a 400 error or something, and that's it.

But.... How do we handle such cases in Airwire? To make things more specific:

1. How do we handle Laravels policy validation in Airwire components?
2. How do we handle authentication related validation in Airwire components?
3. How do we handle custom business logic validation in Airwire components, and what should be returned when something goes wrong (the 400 status code)?

Thank you for reading and commenting :)

Bob

I would like to work on porting it to php 7.4 . Is it possible to give a try or do airwire is constrained to php 8 ?

Without having at least one airwire component you can't compile your assets, I struggled almost 4 days until I decided to try to create a component first then I was able to compile my assets

Really awesome project, can't wait to try this out in a more official capacity. Thank you for creating it.

But I did notice one thing that could be improved upon.

I mentioned in another comment I wrote a Laravel package for Svelte that has many similar problems to solve. My package compiles each Svelte component in your project into bite sized js file, and then loads that file automatically if you use the tag in blade.

So we need to map Blade HTML tags to these compiled JS files. You have to do the same for Blade tags and PHP files, as does Livewire.

I looked at several other projects as inspiration:

• Spatie's BladeX package (which serves as the foundation for Laravel's Blade Components)
• Laravel's Blade Components
• Livewire

There are three main approaches here:

1. Having the user define these mappings in a ServiceProvider

• The approach Spatie Blade X and Airwire took
• The easiest to implement, yet the most annoying for the user.

2. Use a Naming Convention, Standard Locations, Etc.

• Laravel Blade Components basically took Spatie BladeX, but then added a naming convention on top
• By prefixing an x- in front of the component name, and doing some Studly/Camel-case conversion, Laravel knows to check the /resources/views/components folder

3. Build A Manifest File Automatically

• This is the approach Livewire takes, and the approach I stole for my package
• The user doesn't have to define the components in a ServiceProvider
• The package generates a manifest file that loads the component-to-tag mappings
• Check out bootstrap/cache/livewire-components.php

I would love to see Airwire use the manifest approach outlined above and remove that annoying middle step for the user.

Happy to help implement/submit a PR.

Have you considered this at all? See any downsides?

• Vue demo
• Alpine demo
• Delete button
  • Report arg resolved from an id

Greetings,

I love the idea of this being a REST API Wrapper component based. Is It possible to use something like this with NextJS? Where the backend and the frontend might be in different servers?

Hi,

I'm a big fan of Svelte, and Airwire looks interesting to me.

I'm not sure if I can use Airwire with Svelte, because Svelte outputs vanilla js.

Svelte is a radical new approach to building user interfaces. Whereas traditional frameworks like React and Vue do the bulk of their work in the browser, Svelte shifts that work into a compile step that happens when you build your app.

So, is it possible to combine those two?

Thanks! Jeroen

e.g. Airwire::definition(User::class)