this.somevalue always returns undefined -
good morning :)
not sure if this is a issue (not really a bug) in sails v1.0 or sails-postgresql - when using the postgres datastore - if you define a primary key in the model def, but the attribute definition for that pK doesn't include required: true, sails lifts without any error/warning. Only when you try to use that model in code OR when you stop the server do you get an error stating data store identity does not exist.
...
primaryKey: 'id2',
attributes: {
id2: {
type: 'number',
required: true //if required:true is omited, sails lifts with no warning, but model is not accessible
},
}
... try {
var a = await SomeModel.find().limit(10);
} catch(err) {
console.log(err)
}name: 'UsageError',
code: 'E_INVALID_ARGINS',
problems: [Array] } },
isOperational: true,
adapterMethodName: 'find',
modelIdentity: 'SomeModel',
raw:
{ UsageError: Could not run select() because of 2 problems:
------------------------------------------------------
• "datastore" is required, but it was not defined.
• "models" is required, but it was not defined.
------------------------------------------------------
In v0.12 I am able to create blueprint routes with controller subfolder path name but in v1.0 it's not working. For example, I have controller in v1 sub directory like /api/controller/v1/DemoController.js . For this blueprint autogenerated api path is /api/v1/demo in Sails v0.12 but its not working in v1. In Sails v1 its working on path /api/demo. Is there any solution of my problem?
@newari i just did a check and created a test example of this in api/controllers/v1/DemoController.js
i put a test function in there
module.exports = { test: (req, res) => res.json({ it: 'works!'})} it worked for GET 'http://localhost:1337/v1/demo/test
did you check and see if in config/blueprints.js you have actions: true ?
is it also working for find method(default blueprint action ) from your side?
it works if you take out the v1
is it a common practice to version the models?
(i'm still a relatively new programmer and am unfamiliar with a lot of things)
that makes sense if you want to version the models
yeah i'm stumped as well, haven't needed to do that yet with the models. if you don't need to "version" them, but just need to call the default routes for them, they're all accessible though. i guess the other option is to include custom actions in your controllers to keep the url consistent (having v1,v2,etc. in it versus just api/demo1, api/demo2)
In v0.12 I am able to create blueprint routes with controller subfolder path name but in v1.0 it's not working. For example, I have controller in v1 sub directory like /api/controller/v1/DemoController.js . For this blueprint autogenerated api path is /api/v1/demo in Sails v0.12 but its not working in v1. In Sails v1 its working on path /api/demo. Is there any solution of my problem? @mikermcneil Help me please.