guest271314 (2019-06-17T14:40:06.000Z)
guest271314 at gmail.com (2019-06-17T16:05:57.503Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit or even notepad can do that. Can the editor not handle basic search and replace (https://plnkr.co/edit/xiLQRX?p=preview)? Does any code get written by archaic paper and pencil when the power goes out and reliance on a specific text editor or "refactoring tools" cannot be sustained, does the generator get turned on so that the text editor can check for mistakes, or is that a signal to take the rest of the day off? Why use a text editor or IDE or refactoring tools that do not do what you want them to do? Roll your own editor that does exectly what you want it to do? How does ```nameof``` in JavaScript solve issues or lead to expected output at a text editor?
guest271314 at gmail.com (2019-06-17T15:10:57.193Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit or even notepad can do that. Does any code get written by archaic paper and pencil when the power goes out and reliance on a specific text editor or "refactoring tools" cannot be sustained, does the generator get turned on so that the text editor can check for mistakes, or is that a signal to take the rest of the day off? Why use a text editor or IDE or refactoring tools that do not do what you want them to do? Roll your own editor that does exectly what you want it to do? How does ```nameof``` in JavaScript solve issues or lead to expected output at a text editor?
guest271314 at gmail.com (2019-06-17T15:09:22.403Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit or even notepad can do that. Does any code get written by archaic paper and pencil when the power goes out and reliance on a specific text editor or "refactoring tools" cannot be sustained, does the generator get turned on so that the text editor can check for mistakes, or is that a signal to take the rest of the day off? Why use a text editor or IDE or refactoring tools that do not do what you want them to do? Roll your own editor that does exectly what you want it to do?
guest271314 at gmail.com (2019-06-17T15:08:58.552Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit or even notepad can do that. Does any code get written by archaic paper and pencil when the power goes out and reliance on a specific text editor or "refactoring tools" cannot be sustained, does the generator get turned on so that the text editor can check for mistakes, or is that a signal to take the rest of the day off? Why use a text editor or IDE or refactoring tools that do not do what you want them to do? Roll your own editor that does exectly what you want it to do
guest271314 at gmail.com (2019-06-17T15:05:26.067Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit or even notepad can do that. Does any code get written by archaic paper and pencil when the power goes does and reliance on a specific text editor or "refactoring tools" cannot be sustained, does the generator get turned on so that the text editor can check for mistakes, or is that a signal to take the rest of the day off? Why use a text editor or IDE or refactoring tools that do not do what you want them to do? Roll your own editor that does exectly what you want it to do
guest271314 at gmail.com (2019-06-17T14:52:59.395Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit can do that. Does any code get written by archaic paper and pencil when the power goes does and reliance on a specific text editor or "refactoring tools" cannot be sustained, does the generator get turned on so that the text editor can check for mistakes, or is that a signal to take the rest of the day off?
guest271314 at gmail.com (2019-06-17T14:51:31.108Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit can do that. Does any code get written by archaic paper and pencil when the power goes does any code and reliance on a specific text editor to "refactor" cannot be sustained, or is that a signal to take the rest of the day off?
guest271314 at gmail.com (2019-06-17T14:48:44.139Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ``` y ```, even a basic text editor such as gedit can do that.
guest271314 at gmail.com (2019-06-17T14:47:01.890Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'``` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit can do that.
guest271314 at gmail.com (2019-06-17T14:46:44.274Z)
> In VSCode, if you rename ‘foo’ to ‘bar’ at /*1*/, you get this: How is VSCode related to JavaScript? Is the proposal really based on creating ```nameof``` in JavaScript to workaround output at a text editor? Why not file a bug with the individuals who write the code for VSCode or just write a text editor code from scratch which does what you want as to "refactoring"? Or write the code by hand and test the code to avoid having to rely on _any_ text editor to catch your mistakes? If no mistakes will be made as to writing the identifier ```y``` next to ```nameof``` then no mistakes should be make writing the string ```'y'```` at each location where the identifier as a string is found. As for replacing the named identifier in a text editor, simply include surrounding space characters around the identifier when finding and replacing ```\sy\s```, even a basic text editor such as gedit can do that.