Naor Peled

> Looks like this is not working as expected. We are trying to add [entity](https://github.com/jeremydaly/dynamodb-toolbox/blob/3e7cda83fe766722c9b5dac20a5f1ab888ab1c2e/docs/docs/table/methods.md#scan) into `scan` and `query`, but it doesn't seem to fix the issue. > > >...

> > At the moment what you can do is add the entity name (_et by default) field with the entity name and it would be parsed properly, just make...

@ThomasAribart, will you have time to look into this?

@rbdmorgan @dburdan will review this in a bit :)

Not 100% sure wether we want to remove the attribute if provided an empty array. @jeremydaly wdyt?

> @naorpeled, let's add an option to the `put`, `update` and `putBatch` methods to allow for skipping the entity schema check. > > Maybe `strict: false`? > > Also, all...

Hey @ahmad-ali14, lately, I've added an option that allows you not to throw an error when an unmapped field is provided, but it does filter it. It's called `strictSchemaCheck`. An...

Hey, thanks for opening this issue. I'll be closing it for now because it doesn't seem like an issue in the library itself. Let me know if you have any...

I'll be closing this for now, if anyone thinks that this needs to be re-opened, please let me know 🙏

Hey, thanks for opening this issue! I've added a test that covers this, and also tested it on production data with the latest version of the library. This issue seems...