How can not-defined attributes(arbitrary data) be allowed?

[anselmo-coolstay]

Node version: 16.16.0 Sails version (sails): 1.5.2 ORM hook version (sails-hook-orm): 4.0.1 Sockets hook version (sails-hook-sockets): 2.0.1 Organics hook version (sails-hook-organics): Not used Grunt hook version (sails-hook-grunt): 5.0.0 Uploads hook version (sails-hook-uploads): Not used DB adapter & version (e.g. sails-mysql@5.55.5): Not used Skipper adapter & version (e.g. skipper-s3@5.55.5): Not used

---

Hi. I'm using MongoDB and sails-mongo v2.0.0.

According to https://sailsjs.com/documentation/concepts/models-and-orm/model-settings#?schema, not-defined attribute(arbitrary data) can be allowed if config.models.schema is set to false. But, I failed to do that with the below message when creating a record to a model:

WARNING: Automatically trimmed extraneous values!
In call to addMyModel(), 1 of the provided values (notDefinedAttribute) does not correspond with any recognized input.
Please try again without the extra value, or check your usage and adjust accordingly.

In addition, controllers also remove not-defined attributes when it is called thru routes.

How can I allow it?

[sailsbot]

@anselmo-coolstay Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

  ---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.