innetto / inertia-vue-lab Goto Github PK

1. [Laravel] The challange is: Its common accept just one type in prop validation, but if we build a custom input that can be a text input and number when used inside a form?

We can define like modelValue: [String, Number]

1. [Laravel] The challange is: Item needs to be formally developed as a class. Following MVC concepts, make Model and Controller at first and then, use a Factory and seeds to persist fake data in database.

_Use factory to create a "shape" to persist data in db is a common challange in Laravel. When we're creating our project we need to think about the concepts of MVC pattern. Model to represent our database in high level. View to create, edit, persist and delete data. Controller to be like a "bridge" between model and view. _

1. [VueJs] The challange is: A table component needs to be used by any other components. So it need to receive by props the columns and data to build the body table.

Reuse components in our application is really useful to avoid code repetitions around our project. Take a look at the solution on commit

1. [INERTIA] The challange is:

• Two props are renderized into a controller method index. But, just one prop is loaded on first visit. The other one is only loaded when required (lazy).

This challange shows how inertia can make a helpful performance optimization with partial reload. We can show only the data needed in the visit using lazy loading render props.

1. [VueJs] The challange is: Use the Jetstream Dialog Modal component in a custom component that can receive title, content and footer from any child component.

It makes a code without repetition of import and extra lines that we just need to write once

1. [VueJs] The challange is: As we built in issue #7, we need to improve our table to receive any html element inside our table in a new cell. For example: Our table just render the columns and data (th/td). But if the parent component needs the table render a edit button, or a delete or any html element else? If we define a button html inside the table, every table parent will render the button and that certainly is not the expected behavior if we are talking about a custom reusable table.

We can use scoped slot to implement our challange. Table define a named slot and the parent component just implement this named slot inside tag. Take a lock forward

1. [Laravel] The challange is: In a table, select items to checkout in another page, and then come back to the previous page without loosing data selected. Transfering page in client side only.

_We can store data in client side in many ways, but in this case, even we can use Pinia, Vuex or other plugins to work with Inertia, this challange doent require such complex solution. So quick and clear we can use local storage to keep the data saved in url changes. See the entire solution on commit.

1. [Laravel] The challange is: Validate data received from client using Laravel FormRequest

When we use forms to receive data from browser, we have to concert about just send to database validated data to avoid mysql errors.