set workspace for java script for sublime text 3 in mac

Set workspace for java script for sublime text 3 in mac how to#

The only projects that had the problem you talk about were Net Core and some plain old C# before Core, I've maintained Angular and before that Java, older Delphi versions and even PHP. I also maintain a lot of React code, used to work on. I currently work in Kotlin with IntelliJ where sadly the only working IDE is IntelliJ,but you can build it just fine and even fix bugs using whatever editor you want. > Do I have to spin up a whole session of the IDE just to run my test suite? Do I have to dig through eleven nested GUI settings dialogues to find out what the command to build the damn project is, just so I can tweak a build parameter?Ĭan you say what language/platform you talk abojt here?

In fact, insofar that they ever did (generally in GUI builders, which, what with the web and languages like java and Adobe Air and silverlight falling by the wayside in the past few years for front-end dev - are kinda dead), the new takes on such tools all very explicitly keep the whole 'actually this just edits a text file of some sort and this automated click-the-GUI-together tool is bending over backwards to ensure that the underlying file looks as close as possible to what you would write by hand. What are you on about? IDEs don't abstract such details away to extreme degrees. (it better be, in the sense that trying to run the build by hand or by patching a bunch of shell scripts together is almost 100% correlated with very low quality dev teams in my experience). If you ditch your IDE, _nothing_ whatsoever would change: Your build is _still_ based on a build tool. No, it's `mvn install` or `mvn build` or whatever take on 'build' you are looking for specifically. > Do I have to dig through eleven nested GUI settings dialogues to find out what the command to build the damn project is, just so I can tweak a build parameter?

Set workspace for java script for sublime text 3 in mac how to#

IDEs (again, this is mostly speaking from the perspective of the java ecosystem) use build tools as project definitions, and those build tests all know how to run the test suite from the command line. I've never observed 'I only know how to run my tests inside the IDE'. I'm not saying that's a good idea, just saying that I have seen that in real (as in, for pay and for real eyeballs) dev teams. because the tests require a database engine that isn't installed on your development machine. But in highly CI-based situations, the answer is still no, but you DO need the CI system to be up, and the only way to run a test at all is to just commit something and see the CI system run it, e.g. In the java ecosystem at least, the answer is no. Do I have to spin up a whole session of the IDE just to run my test suite?