cosmosdb | Consistent StatusCodes.NotFound handling for Item.ts operations

[nvictoros]

Is your feature request related to a problem? Please describe.

• It is frustrating that read in Item.ts does not throw an error for StatusCodes.NotFound, but the other operations (e.g. delete) do. This is frustrating because:
  • it makes generic error handlers more complex than necessary
  • it is not documented anywhere that this is the case, which means you have to look at the code in this repo to understand why one does not throw an error and the others do
• This difference in error handling for StatusCodes.NotFound is caused by this line where the error is caught and not thrown for read, and the error is instead is returned as the response.

Describe the solution you'd like

• For read and the other operations to have a consistent way of handling errors from ClientContext, or at least just for StatusCodes.NotFound

Describe alternatives you've considered

• Document this difference for the handling of StatusCodes.NotFound so that it is clear for developers

Additional context
Add any other context or screenshots about the feature request here.

require('dotenv').config();
const fs = require('fs');
const { CosmosClient } = require('@azure/cosmos');

const client = new CosmosClient({ endpoint: process.env.ENDPOINT, key: process.env.KEY });
const database = client.database(process.env.DATABASE);
const container = database.container(process.env.CONTAINER);

async function main() {
  console.log('Reading item');
  const item = await container.item('wrong-id').read();
  console.log('Item with wrong id resolved with status: ', item.statusCode);

  try {
    const deletedItem = await container.item('wrong-id').delete();
    console.log('Delete item resolved with status: ', deletedItem.statusCode);
  } catch (error) {
    console.error('Deleting item rejected with error: ', error);
  }
}

main()
  .then(() => { console.log('Exiting...'); process.exit(0); })
  .catch((error) => { console.error(error); process.exit(1); })

[v1k1]

To honor back ward compatibility, we have decided to update documentation and make accept this behavior.

[gkan144]

That is ok for now. But would it be possible to make the read and delete functionalities consistent in a future major version bump?