Redundancy between uri and bucket+remotePath ?

[awhitford]

Consider the following code:

  Future<FirebaseImageObject> get(String uri, FirebaseImage image) async {
    List<Map> maps = await db.query(
      table,
      columns: null,
      where: 'uri = ?',
      whereArgs: [uri],
    );
    if (maps.length > 0) {
      FirebaseImageObject returnObject =
          new FirebaseImageObject.fromMap(maps.first);
      returnObject.reference = getImageRef(returnObject, image.firebaseApp);
      if (CacheRefreshStrategy.BY_METADATA_DATE == this.cacheRefreshStrategy) {
        checkForUpdate(returnObject, image); // Check for update in background
      }
      return returnObject;
    }
    return null;
  }

  StorageReference getImageRef(
      FirebaseImageObject object, FirebaseApp firebaseApp) {
    FirebaseStorage storage =
        FirebaseStorage(app: firebaseApp, storageBucket: object.bucket);
    return storage.ref().child(object.remotePath);
  }

The code seems to be using bucket and remotePath to rehydrate the uri into a StorageReference. Why not simply call FirebaseStorage.getReferenceFromUrl? (And then you can avoid the redundancy of bucket and remotePath.)

I also see that the code is leveraging the firebaseApp, but is that necessary when you have a fully qualified Uri?