user defined warning in typescript
up vote
0
down vote
favorite
I want to add code just temporary and remove it before I do commit. How to create user defined warning in typescript so compiler (or build server) will let me know that this code is still there. I don't want to forget about it. In C# there is #warning, is there something similar in TypeScript?
Example:
foo()
// #warning: remove next line before commit, it is just for develop purposes
return true;
return someLogic(); // just this line should be there
typescript
asked Nov 9 at 14:02
Peter Dub
679
add a comment |
up vote
0
down vote
favorite
I want to add code just temporary and remove it before I do commit. How to create user defined warning in typescript so compiler (or build server) will let me know that this code is still there. I don't want to forget about it. In C# there is #warning, is there something similar in TypeScript?
Example:
foo()
// #warning: remove next line before commit, it is just for develop purposes
return true;
return someLogic(); // just this line should be there
typescript
asked Nov 9 at 14:02
Peter Dub
679
2
In general, this is a bad idea. You should use external configuration (e.g. looking for aDEVELOPMENTenvironment variable) to toggle the behaviour, otherwise you have to keep editing the file just to run unit tests.
– jonrsharpe
Nov 9 at 14:04
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to add code just temporary and remove it before I do commit. How to create user defined warning in typescript so compiler (or build server) will let me know that this code is still there. I don't want to forget about it. In C# there is #warning, is there something similar in TypeScript?
Example:
foo()
// #warning: remove next line before commit, it is just for develop purposes
return true;
return someLogic(); // just this line should be there
typescript
asked Nov 9 at 14:02
Peter Dub
679
I want to add code just temporary and remove it before I do commit. How to create user defined warning in typescript so compiler (or build server) will let me know that this code is still there. I don't want to forget about it. In C# there is #warning, is there something similar in TypeScript?
Example:
foo()
// #warning: remove next line before commit, it is just for develop purposes
return true;
return someLogic(); // just this line should be there
typescript
typescript
asked Nov 9 at 14:02
Peter Dub
679
asked Nov 9 at 14:02
Peter Dub
679
asked Nov 9 at 14:02
Peter Dub
679
asked Nov 9 at 14:02
Peter Dub
679
asked Nov 9 at 14:02
Peter Dub
679
679
2
In general, this is a bad idea. You should use external configuration (e.g. looking for aDEVELOPMENTenvironment variable) to toggle the behaviour, otherwise you have to keep editing the file just to run unit tests.
– jonrsharpe
Nov 9 at 14:04
add a comment |
2
In general, this is a bad idea. You should use external configuration (e.g. looking for aDEVELOPMENTenvironment variable) to toggle the behaviour, otherwise you have to keep editing the file just to run unit tests.
– jonrsharpe
Nov 9 at 14:04
2
2
In general, this is a bad idea. You should use external configuration (e.g. looking for a
DEVELOPMENT environment variable) to toggle the behaviour, otherwise you have to keep editing the file just to run unit tests.– jonrsharpe
Nov 9 at 14:04
In general, this is a bad idea. You should use external configuration (e.g. looking for a
DEVELOPMENT environment variable) to toggle the behaviour, otherwise you have to keep editing the file just to run unit tests.– jonrsharpe
Nov 9 at 14:04
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Since type errors don't block code generation, you can write a dummy line of code that produces a type error, for example:
let a: "remove me before commit" = "";
answered Nov 11 at 4:09
Matt McCutchen
13k719
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Since type errors don't block code generation, you can write a dummy line of code that produces a type error, for example:
let a: "remove me before commit" = "";
answered Nov 11 at 4:09
Matt McCutchen
13k719
add a comment |
up vote
1
down vote
Since type errors don't block code generation, you can write a dummy line of code that produces a type error, for example:
let a: "remove me before commit" = "";
answered Nov 11 at 4:09
Matt McCutchen
13k719
add a comment |
up vote
1
down vote
up vote
1
down vote
Since type errors don't block code generation, you can write a dummy line of code that produces a type error, for example:
let a: "remove me before commit" = "";
answered Nov 11 at 4:09
Matt McCutchen
13k719
Since type errors don't block code generation, you can write a dummy line of code that produces a type error, for example:
let a: "remove me before commit" = "";
answered Nov 11 at 4:09
Matt McCutchen
13k719
answered Nov 11 at 4:09
Matt McCutchen
13k719
answered Nov 11 at 4:09
Matt McCutchen
13k719
answered Nov 11 at 4:09
Matt McCutchen
13k719
13k719
add a comment |
add a comment |
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%2f53227184%2fuser-defined-warning-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
2
In general, this is a bad idea. You should use external configuration (e.g. looking for a
DEVELOPMENTenvironment variable) to toggle the behaviour, otherwise you have to keep editing the file just to run unit tests.– jonrsharpe
Nov 9 at 14:04