StrongLoop general chat. For LoopBack help, see https://gitter.im/strongloop/loopback
Error creating Test2 account { ValidationError: The
Account instance is not valid. Details: username is invalid (value: "test2"); email is invalid (value: "test2@test.com").
@bajtos I am trying to setup micro-services with loopback and remote connector and there came a scenario where I had to pass the accessToken between various services. I knew that loopback:3 by default support's the options argument and also came across https://github.com/strongloop/strong-remoting/pull/430 PR which says that options: {passAccessToken: true} will allow the connector to pass the token between services.
Hence, I tried everything and nothing worked, then went to dig out the actual reason why it wasn't working and came across https://github.com/strongloop/strong-remoting/blob/master/lib/rest-adapter.js#L49 line of code, which I believe is culprit. So I made few changes in my setting file and now token are being passed properly.
Earlier
"serviceAgreement": {
"url": "http://localhost:3000/api",
"name": "xxx",
"connector": "remote",
"options": {
"passAccessToken": true
}
}Working Solution:
"serviceAgreement": {
"url": "http://localhost:3000/api",
"name": "xxx",
"connector": "remote",
"options": {
"rest": {
"passAccessToken": true
}
}
}Do you think this is a correct workaround? Will this break anything or not?
Hi,
Can anyone show me setup / config for model relations and how I can create a model and its relations in one call?
Posted a query on stackoverflow with my current config https://stackoverflow.com/questions/52090245/loopback-insert-model-and-its-relational-data
but is it possible to do Event Sourcing/CQRS with loopback?
Until this is resolved anyone with strong-cluster-control installed will get this report when running npm audit:
Low Prototype Pollution
Package lodash
Patched in >=4.17.5
Dependency of strong-supervisor
Path strong-supervisor > strong-cluster-control > lodash
More info https://nodesecurity.io/advisories/577
https://github.com/rahulrkr08/lb4-rest-sample
configure your package.json like
"dev": "parallelshell \"npm run build:watch\" \"gulp StartServer\"",
and paste below code in gulpfile and you are good to go
const { src, series, parallel } = require('gulp');
const nodemon = require('gulp-nodemon');
const logger = require('gulp-logger');
function StartServer(cb) {
nodemon({
script: './index.js',
done: cb,
watch: ['./dist', './index.js']
})
.on('readable', function () {
console.log(process.stdout);
});
}
exports.StartServer = StartServer
Heya Folks, I'm using strong-soap server to host a web service that talks to a downstream rest api. The response I'm getting is not having correct tag name prefix for first element after soap:body,
I believe the responsible code for this is
if (descriptor.form === 'unqualified') {
elementName = name;
nsContext.pushContext();
nameSpaceContextCreated = true;
} else if (descriptor.qname) {
nsContext.pushContext();
nameSpaceContextCreated = true;
// get the mapping for the namespace uri
let mapping = nsContext.getPrefixMapping(descriptor.qname.nsURI);
let newlyDeclared = false;
// if namespace not declared, declare it
if (mapping === null || mapping.declared === false) {
newlyDeclared = true;
mapping = declareNamespace(nsContext, null,
descriptor.qname.prefix, descriptor.qname.nsURI);
}
// add the element to a parent node
let prefix = mapping ? mapping.prefix : descriptor.qname.prefix;
elementName = prefix ? prefix + ':' + name : name;
// if namespace is newly declared add the xmlns attribute
if (newlyDeclared) {
xmlns = prefix ? 'xmlns:' + prefix : 'xmlns';
}
}in this one, my elements descriptor has qname but its prefix is undefined, any ideas ?
