config/blueprints.js > defaultLimit doesn't affect populated associations

[krawa76]

Node version: 10.13.0
Sails version (sails): 1.2.2
ORM hook version (sails-hook-orm): 2.1.1
Sockets hook version (sails-hook-sockets): 2.0.0
Organics hook version (sails-hook-organics): n/a
Grunt hook version (sails-hook-grunt): 4.0.0
Uploads hook version (sails-hook-uploads): n/a
DB adapter & version (e.g. sails-mysql@5.55.5): sails-mongo@1.0.1
Skipper adapter & version (e.g. skipper-s3@5.55.5): n/a

---

Model (Project.ts)

  module.exports = {
    attributes: {
      name: {type: 'string', required: true},
      apps: {
        collection: 'appInstance',
        via: 'projectId',
      },
    },
  };

config/blueprints.js:

...
  defaultLimit: Number.MAX_SAFE_INTEGER,

Issue: call to http://localhost:1337/project populates the apps collection with {limit: 30} condition, regardless of the number specified for defaultLimit.

Looks like the reason for this is:

sails/lib/hooks/blueprints/parse-blueprint-options.js

Line 48 in 8fb5774

var DEFAULT_POPULATE_LIMIT = 30;

The following code fixes the issue (same approach as

sails/lib/hooks/blueprints/actionUtil.js

Line 28 in 8fb5774

var DEFAULT_POPULATE_LIMIT = req._sails.config.blueprints.defaultLimit || 30;

)

(.../lib/hooks/blueprints/parse-blueprint-options.js)
var DEFAULT_LIMIT = req._sails.config.blueprints.defaultLimit || 30;
var DEFAULT_POPULATE_LIMIT = DEFAULT_POPULATE_LIMIT;

Could you include the fix to the next patch? Thanks.

[sailsbot]

@krawa76 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.

[johnabrams7]

Hi @krawa76 - thanks for the detailed info and workaround.
Officially, the latest version of Sails has moved away from defaultLimit, alternatively going with parseBlueprintActions instead. We recently had a similar issue for defaultLimits that can provide further details and alternative approaches.

[krawa76]

Cool, didn't know that the parseBlueprintOptions existed. Works, thanks a lot!