How to use stringPropertyInitialization with Object.assign in Typescript
I have a class like
export class Config{
public doSomething: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
Passing data to constructor this way is really easy and IntelliSense is smart enough to not allow developers creating new instance of Config
class without specifying doSomething
property, but it does without doSomethingOptionally
.
All this works great, but as soon as I enable strictPropertyInitialization
in tsconfig.json
I get a bunch of errors because doSomething
was not initialized.
What is the best workaround for this?
I don't want to:
- specify default values (objects can be really large)
- use
doSomething: boolean = {} as any;
- assign value in constructor outside the
data
property because there can be a lot of parameters and calling constructor would become too ugly for my taste - Make
doSomething
accept undefined values
typescript tsconfig
add a comment |
I have a class like
export class Config{
public doSomething: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
Passing data to constructor this way is really easy and IntelliSense is smart enough to not allow developers creating new instance of Config
class without specifying doSomething
property, but it does without doSomethingOptionally
.
All this works great, but as soon as I enable strictPropertyInitialization
in tsconfig.json
I get a bunch of errors because doSomething
was not initialized.
What is the best workaround for this?
I don't want to:
- specify default values (objects can be really large)
- use
doSomething: boolean = {} as any;
- assign value in constructor outside the
data
property because there can be a lot of parameters and calling constructor would become too ugly for my taste - Make
doSomething
accept undefined values
typescript tsconfig
add a comment |
I have a class like
export class Config{
public doSomething: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
Passing data to constructor this way is really easy and IntelliSense is smart enough to not allow developers creating new instance of Config
class without specifying doSomething
property, but it does without doSomethingOptionally
.
All this works great, but as soon as I enable strictPropertyInitialization
in tsconfig.json
I get a bunch of errors because doSomething
was not initialized.
What is the best workaround for this?
I don't want to:
- specify default values (objects can be really large)
- use
doSomething: boolean = {} as any;
- assign value in constructor outside the
data
property because there can be a lot of parameters and calling constructor would become too ugly for my taste - Make
doSomething
accept undefined values
typescript tsconfig
I have a class like
export class Config{
public doSomething: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
Passing data to constructor this way is really easy and IntelliSense is smart enough to not allow developers creating new instance of Config
class without specifying doSomething
property, but it does without doSomethingOptionally
.
All this works great, but as soon as I enable strictPropertyInitialization
in tsconfig.json
I get a bunch of errors because doSomething
was not initialized.
What is the best workaround for this?
I don't want to:
- specify default values (objects can be really large)
- use
doSomething: boolean = {} as any;
- assign value in constructor outside the
data
property because there can be a lot of parameters and calling constructor would become too ugly for my taste - Make
doSomething
accept undefined values
typescript tsconfig
typescript tsconfig
edited Nov 20 '18 at 10:51
Enn
asked Nov 20 '18 at 10:45


EnnEnn
1,569818
1,569818
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
One solution is to let the compiler know what properties are initialized via Object.assign
using the definite assignment assertion
export class Config{
public doSomething!: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
exactly what I needed, thanks!
– Enn
Nov 20 '18 at 11:09
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%2f53391292%2fhow-to-use-stringpropertyinitialization-with-object-assign-in-typescript%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
One solution is to let the compiler know what properties are initialized via Object.assign
using the definite assignment assertion
export class Config{
public doSomething!: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
exactly what I needed, thanks!
– Enn
Nov 20 '18 at 11:09
add a comment |
One solution is to let the compiler know what properties are initialized via Object.assign
using the definite assignment assertion
export class Config{
public doSomething!: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
exactly what I needed, thanks!
– Enn
Nov 20 '18 at 11:09
add a comment |
One solution is to let the compiler know what properties are initialized via Object.assign
using the definite assignment assertion
export class Config{
public doSomething!: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
One solution is to let the compiler know what properties are initialized via Object.assign
using the definite assignment assertion
export class Config{
public doSomething!: boolean;
public doSomethingOptionally?: boolean
constructor(data: {
doSomething: boolean,
doSomethingOptionally?: boolean
}) {
Object.assign(this, data);
}
}
answered Nov 20 '18 at 11:04


Titian Cernicova-DragomirTitian Cernicova-Dragomir
60.4k33654
60.4k33654
exactly what I needed, thanks!
– Enn
Nov 20 '18 at 11:09
add a comment |
exactly what I needed, thanks!
– Enn
Nov 20 '18 at 11:09
exactly what I needed, thanks!
– Enn
Nov 20 '18 at 11:09
exactly what I needed, thanks!
– Enn
Nov 20 '18 at 11:09
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%2f53391292%2fhow-to-use-stringpropertyinitialization-with-object-assign-in-typescript%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