Tag: node.js

Issue I tried to follow this example https://docs.strongloop.com/display/public/LB/Connector+hooks var connector = MyModel.getDataSource().connector; connector.observe(‘before execute’, function(ctx, next) { // … next(); }); But the property ‘connector’ seems to be undefined. I need to add a connector hook in the boot script.

Issue I found in the documentation that scopes enable you to specify commonly-used queries that you can reference as method calls on a model. Below i have a categories model. I am trying to create scopes that applies to the

Issue This is a follow up to a previous question. Currently, the api can query from the category and game model which share a relation. For example, through this endpoint /Categories/1001/games/mature I can list all games of fighting category that

Issue This is another follow up to a previous question. There are only two models involved: category and game which share a hasMany relation. Example: The endpoint /Categories/1001/games/mature list all games of fighting category that have mature flag set to

Issue I envision loopback‘s datasources & models as a useful tool for consuming an API, not just for automatically creating a REST API. Pretend I’m using Spotify’s API. I want a command line application that looks up user information on

Issue I have been able to easily set up a basic node.js api with the help of strongloop. I have been able to add custom routes using remoteMethods. However, I am a bit confused in setting up 404 for those

Issue Strongloop api has been great to work with right out of the box. However I am currently trying to make some customizations. I am trying to add to the category model a remote method that returns along with the

Issue I’ve been writing tests for my loopback backend using loopback-testing project. The backend has set loopback-component-storage in order to provide apis to store files in the filesystem. I want to test file upload using the remote api that loopback-component-storage

Issue I created a custom validation for one of my models properties the following way: Model.validateAsync(‘minOsVersion’, validateMinimumOsVersion, {message: ‘Minimum OS Version incorrect’}); function validateMinimumOsVersion(err, done) { var requiredVersion = “some version”; var givenVersion = this.minOsVersion; if (validator.validateSemanticVersionString(givenVersion, requiredVersion) < 0)

Issue I am using form authentication and role based access. I want to make all the subsequent request as an authentication request using the access token. I refer Loopback-example-access-control example, but not get a clear idea. In this example, they

Issue I am trying to create acl rules at run-time for all models. I have form that contain ACL information Like: id, model name, property, accesstype, principalId, (here I am assign roldId from role table). PrincipalType. After submit the form,

Issue In unit testing Loopback it is necessary to use callbacks with the upsert methods. So for example … instead of writing something along the lines of this: before(function () { Student = server.models.Student Course = server.models.Course Course.upsert({id: 1, key:

Issue When updating a related object, I get two completely different behaviors from the same code. For example, a question belongs to a student. I run the code below on two separate machines. Question.observe(‘after save’, function (ctx, next) { var

Issue I am starting to gain grounds with loopback api. Currently I am trying to integrate authentication through social login for my app. I have found three pages that indicate how to accommplish this but they all show this a

Issue I have two models Question and Answer. A Question has many Answers, and an Answer belongs to a Question. Then in Loopback provides a reference to an Answer. What I can’t figure out is how do I then get

Issue I want to update last inserted/updated document(row) in “after save” hook without create new instance of that like this: Model.observe(‘after save’, function (ctx, next) { ctx.someProperty = ‘Foo’; ctx.update(); }); How it possible? Solution I’m not sure what you

Issue I read that embedsMany (in case of non relational db) puts the embedded models in the parent model document. While hasMany creates a new collection of child model and a relation is created between parent collection and child collection.

Issue I don’t have much experience with Strongloop but maybe someone can put me in the right direction. In my model I have information of Clients. The Client must have access to their own record but not to the record

Issue How can I configure an operation hook, such as after save, when linking or unlinking an instance of the foreign model? Using loopback’s example Assembly and Part model: https://docs.strongloop.com/display/public/LB/HasAndBelongsToMany+relations I would like to execute code when adding (or removing)

Issue Any way to strongloop’s /User/login responce can be extended by UserRoles field? By default strongloop return user object with “firstName, lastName, email, id and userName”, i also need userRoles. Solution You can create a remote hook for the built-in

Issue I have generated an app using strongloop and added the following code in user.js // user.js console.log(“came here”); module.exports = function(app) { console.log(app); }; Why I cannot see any console? Why is this file not being included while running

Issue I try to make request to mongoDB: GeoData.find({ include: {relation: ‘Account’} , where: { and: [{ Coordinate: { near: alarm.Geopoint, maxDistance: maxDist.Value, unit: ‘meters’ } }, {Time: {gt: fromTime}}] } },function(err, datas){ _.each(geoDatas, function(val){ console.log(val); //line 1 console.log(val.Account); //line

Issue So, I read the documentation about manage the users. I also comes from this example: link. Then I try to make a model, called user-basic which bases on built-in model User. Here’s the user-basic.json: { “name”: “user-basic”, “base”: “User”,

Issue I’m making a games backend in loopback. I have a user model defined as such. { “name”: “player”, “base”: “User”, “idInjection”: true, “options”: { “validateUpsert”: true }, “properties”: { “name”: { “type”: “string”, “required”: true } }, “validations”: [],