livewire important notes

by Devin Yang
(This article was automatically translated.)

Published - 1 year ago ( Updated - 1 year ago )

Before starting your Livewire journey,
Here are three basic considerations about public properties:

* 100009*1. The property name cannot conflict with the property name reserved for Livewire (for example, $rules or $message)

2. The data stored in the public properties (public properties), for Front-end JavaScript is visible.
Therefore, you should not store sensitive data in it.

3. Attributes can only be JavaScript-friendly data types (string, integer, array, boolean), or one of the following PHP types: Stringable, Collection, DateTime, Model, EloquentCollection.

Tags: laravel livewire

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

laravel

Basic application teaching of jenkins CI Server pipeline on Laravel

Do you want to build a continuous integration and delivery CI Server for Laravel through docker? Execute laravel dusk and phpunit on CI Server to easily handle automated testing and related records. After reading this article, you may find out how simple CI/CD is. I mean basic use.

d-laravel,docker

D-Laravel v1.2.1 version change description (recommended update, must avoid stepping on thunder)

D-Laravel v1.2.1 revision instructions use GuzzleHttp\Client; When posting, there is an access denied problem. If you are upgrading from an older version, you may need to adjust the configuration file in etc/default-ssl.conf (if there is one) Please adjust php:9000 to web:9000, you can adjust it by executing ./console secure once. In the docker-compose configuration file, change the PHP-FPM container to network_mode: "service:web"...

docker, tinkerwell, tinker, laravel

Application of Tinkerwell and docker environment

In fact, I don't use Tinkerwell recently because it keeps costing me money to update. If you want to test the direct ssh host, it’s done, isn’t it?