Showing 7 of 587 result(s)
The Cookie facade defines two additional methods. These methods access other, related, components. These methods exist to simplify accessing related components.
The Input facade defines one extra method. Facades define extra methods to provide simpler access to underlying sub-systems, or to call functions on other, related components.
The Schema facade defines one extra method. Facades define extra methods to provide simpler access to underlying sub-systems, or to call functions on other, related components, or to provide greater testability of the framework components.
The Notification facade defines a few extra methods that can be called without resolving the notification sub-system from the service container. Facades define extra methods to provide simpler access to underlying sub-systems, or to call functions...
The getAttributes method simply returns an array containing all key/value pairs, representing the underlying data contained within the Fluent instance.
Because Macroable depends on both the __call and __callStatic methods to be available for its own use, it is currently not possible to use the Macroable trait in a class that also requires returning a value from either __call or __callStatic...
The $key supplied to the add method should make sense in some context. The examples so far have been fairly arbitrary, and are mainly designed to explain the concepts that are being presented. However, MessageBag instances are most commonly...