tl;dr: We take a look at the Swift language reference, and sure enough, the usage of this backslash-dot notation is called a key-path-expression.
(The question has been sufficiently answered, by this point.)
A more hands-on approach on how to get to that piece of buried documentation:
As you can see from the code you posted, the User class contains a property named email
.
Notice that, assuming you're using Xcode, if you replace return .email
with return
, you get the compile-error "Expected expression path in Swift key path"
, so this is a hint that this backslash-dot notation might have to do with something called a key path.
From that documentation on key-path, we see that we could also have written User.email
(and you can try it out in Xcode with no compiler error).
Understanding the greater context of what's going on in that code:
So, semantically, to understand the meaning of the usernameKey
declaration you're looking at, we might want to understand what a WritableKeyPath
is. In simple, from the documentation, we see that a WritableKeyPath
is: "A key path that supports reading from and writing to the resulting value."
So, we see that the usernameKey
declaration takes in a WritableKeyPath
object and returns a String
that is User.email
.
Furthermore, it's apparent that the User class needs this usernameKey
property in order to conform to the PasswordAuthenticatable
protocol, which was imported on the first line with import Authentication
(if you care to explore there, take a look at Dependencies > Auth 2.0.0 > Authentication > Basic > BasicAuthenticatable.swift).
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…