Loopback4 Model Definition options for mongodb collection name
I am using loopback 4 and trying to configure the Model annotation with properties to configure how the collection is created in Mongo.
I have a Model called say Client and I want the collection in Mongo to be called Clients. The cross over with documentation is confusing, as they reference the properties from v3 in v4 docs.
I have tried this:
import {Entity, model, property} from '@loopback/repository';
@model({
settings: {strict: false},
name: 'client',
plural: 'clients',
options: {
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
@property({
type: 'string',
id: true,
defaultFn: 'uuidv4',
index: true,
})
id: string;
@property({
type: 'string',
required: true,
})
name: string;
@property({
type: 'string',
})
code?: string;
constructor(data?: Partial<Client>) {
super(data);
}
}With no Joy, still creates the collection as the Class name Client
loopbackjs loopback v4l2loopback
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
add a comment |
I am using loopback 4 and trying to configure the Model annotation with properties to configure how the collection is created in Mongo.
I have a Model called say Client and I want the collection in Mongo to be called Clients. The cross over with documentation is confusing, as they reference the properties from v3 in v4 docs.
I have tried this:
import {Entity, model, property} from '@loopback/repository';
@model({
settings: {strict: false},
name: 'client',
plural: 'clients',
options: {
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
@property({
type: 'string',
id: true,
defaultFn: 'uuidv4',
index: true,
})
id: string;
@property({
type: 'string',
required: true,
})
name: string;
@property({
type: 'string',
})
code?: string;
constructor(data?: Partial<Client>) {
super(data);
}
}With no Joy, still creates the collection as the Class name Client
loopbackjs loopback v4l2loopback
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
add a comment |
I am using loopback 4 and trying to configure the Model annotation with properties to configure how the collection is created in Mongo.
I have a Model called say Client and I want the collection in Mongo to be called Clients. The cross over with documentation is confusing, as they reference the properties from v3 in v4 docs.
I have tried this:
import {Entity, model, property} from '@loopback/repository';
@model({
settings: {strict: false},
name: 'client',
plural: 'clients',
options: {
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
@property({
type: 'string',
id: true,
defaultFn: 'uuidv4',
index: true,
})
id: string;
@property({
type: 'string',
required: true,
})
name: string;
@property({
type: 'string',
})
code?: string;
constructor(data?: Partial<Client>) {
super(data);
}
}With no Joy, still creates the collection as the Class name Client
loopbackjs loopback v4l2loopback
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
I am using loopback 4 and trying to configure the Model annotation with properties to configure how the collection is created in Mongo.
I have a Model called say Client and I want the collection in Mongo to be called Clients. The cross over with documentation is confusing, as they reference the properties from v3 in v4 docs.
I have tried this:
import {Entity, model, property} from '@loopback/repository';
@model({
settings: {strict: false},
name: 'client',
plural: 'clients',
options: {
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
@property({
type: 'string',
id: true,
defaultFn: 'uuidv4',
index: true,
})
id: string;
@property({
type: 'string',
required: true,
})
name: string;
@property({
type: 'string',
})
code?: string;
constructor(data?: Partial<Client>) {
super(data);
}
}With no Joy, still creates the collection as the Class name Client
import {Entity, model, property} from '@loopback/repository';
@model({
settings: {strict: false},
name: 'client',
plural: 'clients',
options: {
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
@property({
type: 'string',
id: true,
defaultFn: 'uuidv4',
index: true,
})
id: string;
@property({
type: 'string',
required: true,
})
name: string;
@property({
type: 'string',
})
code?: string;
constructor(data?: Partial<Client>) {
super(data);
}
}import {Entity, model, property} from '@loopback/repository';
@model({
settings: {strict: false},
name: 'client',
plural: 'clients',
options: {
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
@property({
type: 'string',
id: true,
defaultFn: 'uuidv4',
index: true,
})
id: string;
@property({
type: 'string',
required: true,
})
name: string;
@property({
type: 'string',
})
code?: string;
constructor(data?: Partial<Client>) {
super(data);
}
}loopbackjs loopback v4l2loopback
loopbackjs loopback v4l2loopback
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
edited Nov 15 '18 at 12:53
Ronan Rafferty
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
asked Nov 14 '18 at 19:07
Ronan RaffertyRonan Rafferty
15419
15419
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
This is from 2014, but perhaps it still works. Try not putting the mongodb key options
settings: {strict: false},
name: 'client',
plural: 'clients',
mongodb: {
collection: 'clients',
},
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
Tried that, I think maybe they are yet to implement it. I will check the repo when I get a chance. Thanks for your reply!
– Ronan Rafferty
Nov 16 '18 at 15:55
add a comment |
Please note that all model settings must be nested inside settings property, LB4 does not support top-level settings yet.
Also the option plural is not used by LB4 as far as I know.
I think the following code should work for you:
@model({
name: 'client',
settings: {
strict: false
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
// ...
}
UPDATE: I opened a GitHub issue to discuss how to make @model decorator easier to use for users coming from LB3. See https://github.com/strongloop/loopback-next/issues/2142
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307168%2floopback4-model-definition-options-for-mongodb-collection-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is from 2014, but perhaps it still works. Try not putting the mongodb key options
settings: {strict: false},
name: 'client',
plural: 'clients',
mongodb: {
collection: 'clients',
},
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
Tried that, I think maybe they are yet to implement it. I will check the repo when I get a chance. Thanks for your reply!
– Ronan Rafferty
Nov 16 '18 at 15:55
add a comment |
This is from 2014, but perhaps it still works. Try not putting the mongodb key options
settings: {strict: false},
name: 'client',
plural: 'clients',
mongodb: {
collection: 'clients',
},
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
Tried that, I think maybe they are yet to implement it. I will check the repo when I get a chance. Thanks for your reply!
– Ronan Rafferty
Nov 16 '18 at 15:55
add a comment |
This is from 2014, but perhaps it still works. Try not putting the mongodb key options
settings: {strict: false},
name: 'client',
plural: 'clients',
mongodb: {
collection: 'clients',
},
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
This is from 2014, but perhaps it still works. Try not putting the mongodb key options
settings: {strict: false},
name: 'client',
plural: 'clients',
mongodb: {
collection: 'clients',
},
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
answered Nov 15 '18 at 18:40
Marvin IrwinMarvin Irwin
42615
42615
Tried that, I think maybe they are yet to implement it. I will check the repo when I get a chance. Thanks for your reply!
– Ronan Rafferty
Nov 16 '18 at 15:55
add a comment |
Tried that, I think maybe they are yet to implement it. I will check the repo when I get a chance. Thanks for your reply!
– Ronan Rafferty
Nov 16 '18 at 15:55
Tried that, I think maybe they are yet to implement it. I will check the repo when I get a chance. Thanks for your reply!
– Ronan Rafferty
Nov 16 '18 at 15:55
Tried that, I think maybe they are yet to implement it. I will check the repo when I get a chance. Thanks for your reply!
– Ronan Rafferty
Nov 16 '18 at 15:55
add a comment |
Please note that all model settings must be nested inside settings property, LB4 does not support top-level settings yet.
Also the option plural is not used by LB4 as far as I know.
I think the following code should work for you:
@model({
name: 'client',
settings: {
strict: false
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
// ...
}
UPDATE: I opened a GitHub issue to discuss how to make @model decorator easier to use for users coming from LB3. See https://github.com/strongloop/loopback-next/issues/2142
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
add a comment |
Please note that all model settings must be nested inside settings property, LB4 does not support top-level settings yet.
Also the option plural is not used by LB4 as far as I know.
I think the following code should work for you:
@model({
name: 'client',
settings: {
strict: false
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
// ...
}
UPDATE: I opened a GitHub issue to discuss how to make @model decorator easier to use for users coming from LB3. See https://github.com/strongloop/loopback-next/issues/2142
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
add a comment |
Please note that all model settings must be nested inside settings property, LB4 does not support top-level settings yet.
Also the option plural is not used by LB4 as far as I know.
I think the following code should work for you:
@model({
name: 'client',
settings: {
strict: false
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
// ...
}
UPDATE: I opened a GitHub issue to discuss how to make @model decorator easier to use for users coming from LB3. See https://github.com/strongloop/loopback-next/issues/2142
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
Please note that all model settings must be nested inside settings property, LB4 does not support top-level settings yet.
Also the option plural is not used by LB4 as far as I know.
I think the following code should work for you:
@model({
name: 'client',
settings: {
strict: false
mongodb: {
collection: 'clients',
},
},
})
export class Client extends Entity {
// ...
}
UPDATE: I opened a GitHub issue to discuss how to make @model decorator easier to use for users coming from LB3. See https://github.com/strongloop/loopback-next/issues/2142
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
edited Dec 10 '18 at 16:24
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
answered Dec 10 '18 at 16:18
Miroslav BajtošMiroslav Bajtoš
7,0022665
7,0022665
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307168%2floopback4-model-definition-options-for-mongodb-collection-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
