Io语言用户输入(Io language user input)

 如果您希望将数据限制为任何经过身份验证的用户，则需要检查auth !== null 。 
 
 如果希望数据仅限于当前经过身份验证的用户，则需要检查auth.uid == $uid 。 您不需要检查auth == null && auth.uid != $uid因为如果auth变量为null， auth.uid == $uid将评估为false。 但你仍然可以将两者都包括在内。 
 
 实质上， auth != null将数据限制为任何经过身份验证的用户，并且auth.uid != null限制为当前经过身份验证的单个用户。 
 
 现在提供一些额外的课程信息。 
 
 使用Bolt编译器简化通用规则。 
 
 安全规则是灵活的，但它们对于复制通用规则没有太多便利。 为此，您可以使用Bolt编译器 。 
 
 Bolt编译器允许您创建类型并将它们分配给Firebase数据库中的路径。 这些类型充当架构。 您还可以创建抽象通用规则的函数。 
 
 我写了一篇关于用Bolt保护用户数据的博文 。 它通过您需要知道的内容来保证用户数据在Bolt中使用类型和功能进行保护。 
 
isCurrentUser(uid) = auth != null && auth.uid == uid;
isAuthenticated() = auth != null

path /users/$uid {
  read() = isAuthenticated() // any authenticated user can read 
  write() = isCurrentUser($uid); 
}
 
 在上面的示例中，我们重复使用isCurrentUser()函数三次。 这将使更改前进更容易处理。 

You need to check auth !== null if you want the data restricted to any authenticated user.
 
You need to check for auth.uid == $uid when you want the data restricted to the currently authenticated user. You don't need to check for auth == null && auth.uid != $uid because auth.uid == $uid will evaluate to false if the auth variable is null. But you can still include both to be thorough.
 
So essentially, auth != null is restricts the data to any authenticated user, and auth.uid != null restricts to the single currently authenticated user.
 
Now for some extra curricular information.
 
Use the Bolt compiler to simplify common rules.
 
Security Rules are flexible, but they don't have much convenience for reproducing common rules. For that, you can use the Bolt compiler.
 
The Bolt compiler allows you to create types and assign them to paths in your Firebase database. These types act as schema. You can also create functions that abstract common rules.
 
I wrote a blog post on securing user data with Bolt. It goes through what you need to know to keep user data secured with types and functions in Bolt.
 
isCurrentUser(uid) = auth != null && auth.uid == uid;
isAuthenticated() = auth != null

path /users/$uid {
  read() = isAuthenticated() // any authenticated user can read 
  write() = isCurrentUser($uid); 
}
 
In the example above we reuse the isCurrentUser() function three separate times. This will make changes moving forward much easier to deal with.