Note: currently only works on *nix systems (until a powershell script can be created)
With the technique below, you can run node, npm, npx, or yarn commands as if the programs were installed
natively on your system, and you won't even know the difference! This includes any ports that your app or dev process
will start up and use for development, as well as compatibility with persistent npm config --global cli usage.
See more in the Usage section below.
Integrate JMH (Java Microbenchmarking Harness) with Spring (Boot) and make developing and running benchmarks as easy and convinent as writing tests.
Wrap the necessary JMH boilerplate code within JUnit to benefit from all the existing test infrastructure Spring (Boot) provides. It should be as easy and convinent to write benchmarks as it is to write tests.
Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.
“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”
Matt Bridges' answer in full:
The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing
| import sublime_plugin | |
| class FileNameOnStatusBar(sublime_plugin.EventListener): | |
| def on_activated(self, view): | |
| path = view.file_name() | |
| if path: | |
| for folder in view.window().folders(): | |
| path = path.replace(folder + '/', '', 1) | |
| view.set_status('file_name', path) | |
| else: |
