Yeah but why doesnt it infer data to be type:

ts
{Key:string}

instead it infers it to be:

ts
{ Key: string } | null

Me and my friend researched this further and came to conclusion that almost all of the storage methods are wrongly typed, they are being cast wrongly. We think its due to typescript version 4.07 which is bugged, we will make pull request and ask you to update typescript version aswell. This is the bug we are talking about : https://github.com/microsoft/TypeScript/issues/48037 This is example of wrongly typed method in the storage library:

ts
getPublicUrl(
    path: string
  ): {
    data: { publicURL: string } | null
    error: Error | null
    publicURL: string | null
  } {
    try {
      const _path = this._getFinalPath(path)
      const publicURL = `${this.url}/object/public/${_path}`
      const data = { publicURL }
      return { data, error: null, publicURL }
    } catch (error) {
      return { data: null, error, publicURL: null }
    }
  }

Is typed as:

ts
{
    data: { publicURL: string } | null
    error: Error | null
    publicURL: string | null
  }

But should be:

ts
{
  data: null;
  error: Error;
  publicURL: null;
}
| {
data: { publicURL: string };
error: null;
publicURL: string;
};

This is a huge inconvenience for users of this library and requires people that want to use typescript correctly to write a lot of boilerplate.

keeping this in a thread for better house keeping

It will return an error in that case, If not then the whole library itself is typed wrongly not only this part of code