Laravel 9突变器结肠

发布于 2025-01-24 14:10:50 字数 669 浏览 1 评论 0原文

在Laravel 9中，突变器有不同的实现。以下示例来自官方文档。

protected function firstName(): Attribute
{
    return Attribute::make(
        get: fn ($value) => ucfirst($value),
        set: fn ($value) => strtolower($value),
    );
}

但是， colon是什么： get和set是什么？这是PHP 8中的新功能吗？属性的定义:: make是：

public static function make(callable $get = null, callable $set = null): Attribute

原文

In Laravel 9, there’s a different implementation for mutators. The following example is from the official documentation.

protected function firstName(): Attribute
{
    return Attribute::make(
        get: fn ($value) => ucfirst($value),
        set: fn ($value) => strtolower($value),
    );
}

But what is the colon: after get and set? Is this a new feature in PHP 8? The definition of Attribute::make is:

public static function make(callable $get = null, callable $set = null): Attribute

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

尝蛊 2025-01-31 14:10:50

new noreferrer”> new norguments 是PHP中的一个新功能8.0。

在具有简单签名的功能或方法中，它可以用作一种自我文献来指示参数是什么。例如，在您提供的代码中，两个参数都是简单的回调，可以对提供的值执行基本字符串操纵。没有参数名称，阅读代码的人将需要检查方法签名以了解每个参数的作用。

这也是仅在使用具有长签名或复杂默认值的函数或方法时指定所需参数的便捷方法。

例如，htmlspecialchars（）的签名看起来像：

htmlspecialchars(
    string $string,
    int $flags = ENT_QUOTES | ENT_SUBSTITUTE | ENT_HTML401,
    ?string $encoding = null,
    bool $double_encode = true
): string

在以前的版本中，如果您想将double_encode参数更改为false，但将其他参数作为默认，您，您'd必须这样做：

<?php
$escaped = htmlspecialchars(
    "Some text & stuff",
    ENT_QUOTES | ENT_SUBSTITUTE | ENT_HTML401,
    null,
    false
);

除了更加混乱之外，我们还拥有非直觉的值，例如null和false。过去，一种典型的方法是将变量用于诸如$ is_double_encoded = false之类的值。但是借助命名参数，它看起来像这样：

<?php
$escaped = htmlspecialchars(
    "Some text & stuff",
    double_encode: false
);

我们不仅跳过了保持其默认值的参数，而且double_encode参数清楚地标有其名称，我们可以从中推断出其用法。

Named arguments are a new feature in PHP 8.0.

In functions or methods with simple signatures it can serve as a sort of self-documentation to indicate what the arguments are. For example in the code you provided, both arguments are simple callbacks that perform basic string manipulation on the provided value. Without the argument names, someone reading the code would need to check the method signature to know what each argument does.

It’s also a convenient way to only specify needed arguments when using functions or methods with long signatures or complex default values.

For example, the signature for htmlspecialchars() looks like this:

htmlspecialchars(
    string $string,
    int $flags = ENT_QUOTES | ENT_SUBSTITUTE | ENT_HTML401,
    ?string $encoding = null,
    bool $double_encode = true
): string

In previous versions if you wanted to change the double_encode argument to false, but leave the other arguments as default, you’d have to do this:

<?php
$escaped = htmlspecialchars(
    "Some text & stuff",
    ENT_QUOTES | ENT_SUBSTITUTE | ENT_HTML401,
    null,
    false
);

In addition to being more cluttered, we're left with non-intuitive values like null and false. A typical approach in the past was to use variables for the values such as $is_double_encoded = false. But with named arguments it looks like this:

<?php
$escaped = htmlspecialchars(
    "Some text & stuff",
    double_encode: false
);

Not only do we skip the parameters which keep their default value, but the double_encode parameter is clearly labelled with its name, from which we can infer its usage.

回复收藏 0 原文

~没有更多了~