Both no bucket and no file are return 404 and NotFound. So I can't handle these.

[username1103]

Hi, I'm use this library with nodejs.

  const [result] = await this.client
    .bucket(this.config.options.bucket)
    .file(key)
    .download();

  return new File(key, result);

I want to handle no bucket error and no such key error.
When connected to actual cloud storage, I was able to distinguish it through messages. "The specified bucket does not exist", "No such object".

However, when using fake-gcs-server, even if there is no bucket or no object, the same error 404 ApiError: NotFound is provided, so it cannot be distinguished.

I received message "No such object" if object does not exist and bucket exists in actual cloud storage.
And received message "The specified bucket does not exist" if bucket does not exists in acual cloud storage.

Is there a way to handle both errors?

[fsouza]

We should try to make the messages the same (though that's very tricky as the actual error messages are not part of the API, so they could change at anytime).