如何在Firebase评分系统中限制用户单步道仅可评分一次

Hey Erik, great question! Let's break down how to fix this "multiple ratings per user per trail" issue—you'll need to tweak both your Firebase data structure and your Android code to make this work reliably.

First: Adjust Your Firebase Data Structure #

The root problem is your current setup doesn't track which user rated which trail uniquely. Here's how to restructure it to enforce one rating per user per trail:

Old (Problematic) Structure

trails
  - trailId_123
    - ratings
      - randomPushKey_1: { userId: "user_456", score: 4 }
      - randomPushKey_2: { userId: "user_456", score: 5 } // Duplicate rating!
    - averageRating: 4.5

New (Fixed) Structure

Use the user's UID as the document key under a userRatings subcollection—this ensures each user can only have one entry per trail:

trails
  - trailId_123
    - userRatings
      - user_456: { score: 4, timestamp: 1690000000 } // Unique per user
      - user_789: { score: 5, timestamp: 1690001000 }
    - averageRating: 4.5

This structure makes it impossible to have duplicate ratings from the same user (Firebase will overwrite the existing entry if you try, but we'll add code to prevent that entirely).

Second: Modify Your Android Code #

Based on your XXXActivity that implements RatingDialogListener, here's what to update:

1. Check if the User Has Already Rated the Trail

Before showing the rating dialog, verify if the user has an existing rating for this trail:

FirebaseFirestore db = FirebaseFirestore.getInstance();
String currentUserId = FirebaseAuth.getInstance().getCurrentUser().getUid();
String targetTrailId = "your_current_trail_id"; // Replace with your trail ID

// Check for existing rating
db.collection("trails")
  .document(targetTrailId)
  .collection("userRatings")
  .document(currentUserId)
  .get()
  .addOnSuccessListener(doc -> {
      if (doc.exists()) {
          // User already rated this trail—show a warning
          Toast.makeText(this, "You've already rated this trail!", Toast.LENGTH_SHORT).show();
      } else {
          // No existing rating—show the dialog
          showRatingDialog(); // Your existing dialog trigger
      }
  })
  .addOnFailureListener(e -> {
      Toast.makeText(this, "Failed to check rating status. Try again.", Toast.LENGTH_SHORT).show();
  });

2. Handle Rating Submission Correctly

When the user submits a rating, write it to the userRatings subcollection using their UID as the document ID, then update the average rating. For accuracy, use a Firebase Cloud Function to calculate the average (avoids client-side concurrency issues), but here's a client-side fallback for quick testing:

// Assume this is your RatingDialogListener implementation
@Override
public void onRatingSubmitted(int rating) {
    FirebaseFirestore db = FirebaseFirestore.getInstance();
    String currentUserId = FirebaseAuth.getInstance().getCurrentUser().getUid();
    String targetTrailId = "your_current_trail_id";

    // Write the user's rating
    db.collection("trails")
      .document(targetTrailId)
      .collection("userRatings")
      .document(currentUserId)
      .set(new RatingModel(rating, System.currentTimeMillis()))
      .addOnSuccessListener(v -> {
          // Calculate and update average rating
          updateTrailAverageRating(targetTrailId);
          Toast.makeText(this, "Rating submitted!", Toast.LENGTH_SHORT).show();
      })
      .addOnFailureListener(e -> {
          Toast.makeText(this, "Failed to submit rating. Try again.", Toast.LENGTH_SHORT).show();
      });
}

// Helper method to update average rating
private void updateTrailAverageRating(String trailId) {
    FirebaseFirestore db = FirebaseFirestore.getInstance();
    db.collection("trails")
      .document(trailId)
      .collection("userRatings")
      .get()
      .addOnSuccessListener(snapshot -> {
          float totalScore = 0;
          int ratingCount = snapshot.size();

          for (DocumentSnapshot doc : snapshot) {
              RatingModel rating = doc.toObject(RatingModel.class);
              totalScore += rating.getScore();
          }

          float average = totalScore / ratingCount;
          // Update the trail's average rating
          db.collection("trails").document(trailId)
            .update("averageRating", average);
      });
}

// Simple RatingModel class for Firebase serialization
public class RatingModel {
    private int score;
    private long timestamp;

    public RatingModel() {} // Required empty constructor for Firebase

    public RatingModel(int score, long timestamp) {
        this.score = score;
        this.timestamp = timestamp;
    }

    // Getters and setters
    public int getScore() { return score; }
    public void setScore(int score) { this.score = score; }
    public long getTimestamp() { return timestamp; }
    public void setTimestamp(long timestamp) { this.timestamp = timestamp; }
}

3. Add Firebase Security Rules (Critical!)

Prevent users from modifying other people's ratings by adding these rules to your Firestore console:

rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /trails/{trailId}/userRatings/{userId} {
      allow read: if request.auth != null;
      allow write: if request.auth != null && request.auth.uid == userId;
    }
  }
}

Final Note #

You can't fix this with code alone—adjusting the Firebase data structure is essential to enforce the "one rating per user per trail" constraint. The code changes then build on that structure to prevent duplicate submissions and keep the average rating up-to-date.

内容的提问来源于stack exchange，提问作者Erik