Using WebStorm 2019.3.2. I setup a file watcher for prettier, and have it configured with Auto-save edited files to trigger the watcher. It works great, but when I try to use the Local History feature, it has hundred of entries, each time prettier runs.
I could only find in the doc a way to configure the retention of the Local History, not the frequency. Is it possible to reduce the number of entries when a prettier file watcher is enabled?
File watchers or third-party plugins are no longer required for prettier in webstorm 2020.1
changelog
how to configure prettier in webstorm
EDIT:
You can set prettier as default formatter in webstrom 2020.2
changelog
Related
Pretty much title.
Supose I edit the requirements.txt file to add a new package, or to change package versions. When will the environment apply these changes, and what manual steps do I have to take (if any) to make that happen?
The aws documentation on the procedure states that one must simply go through the 'Edit' settings, but in the case I didn't even change the filename is it necessary?
In the MWAA settings, you will change the version of requirements.txt (the name of the file will remain the same). You choose the latest version of the file and save it. As soon as you save it, the MWAA instance will restart automatically to update and install the packages mentioned in the "requirements.txt" file.
Is there any option to set auto configuration in WebStorm (latest version 2020.1)?
Like if I store all the required run configuration details in a file, when I open the WebStorm it should automatically set the run configuration.
Is there any way to do that? Any suggestion here please.
Problem
The question pretty much says it all. I used the plugin: "cf local" to get the .droplet file for my app in PCF. However, I have no idea how to expand or view the contents of the file.
What I tried
I tried adding a .zip at the end, but that did not work.
I tried viewing in NotePad, but that did not work.
Notes
We are using a Diego back-end which prevents us from using "cf files".
It shouldn't matter but we are deploying a .NET application
Related: Is it possible to download all files of an application in Cloud Foundry?
It's a gziped tar archive. Try adding a .tgz or .tar.gz extension. You may need a third party archive tool, I don't know if Windows will open that file by default. 7zip or something comparable should open it.
Daniel was on the right track, however I wanted to post exactly what I used as an alternative to an extraction utility.
I found that the easiest way is to use bash, within Windows. When we installed Github desktop there was an option to use bash and most of us, in my area, have done this.
If you have already installed it then: Goto Preferences an choose your Git-Shell. Under default Shell you can choose between: CMD, Git Bash, Powershell or Custom.
Once that is in place you can navigate to the folder where the .droplet file lives and execute the following command:
tar -xvzf app-name.droplet
This will extract the contents into a folder called "app" in the current directory which has the contents of your asset that would be in PCF.
The documentation for the ember-cli-code-coverage project on Github does not clearly state how exactly to configure and run coverage reports.
The documentation hints that, after installing the addon, you just need to set an environment variable named COVERAGE to true. I interpret that to mean an environment variable in config/environment.js. After running the CLI command ember test I expect to find something saved in a coverage folder at the root of the project, but nothing appears to be generated. My tests run okay without any errors, and with all passing tests.
There are a few statements on Stackoverflow (here, here, and here) that suggest the package works okay. Searching for clear examples or how-to articles appears to be a dead end at the present moment.
I'm trying to get this working using versions:
Ember.js 2.6.0
ember-cli-code-coverage 0.2.2
Windows 10
You need to set the environment variable in the command line environment, not the Ember environment. Run COVERAGE=true ember test.
Side-note: this does seem like a weird choice, requiring a command line environment variable instead of making it configurable in other ways the way ember-cli-blanket does.
This is specific to my current project. But maybe the answers will reveal some more generic solutions.
Here is the situation:
I develop django project on my Windows box
I use SVN to commit to a SVN repository
while developing I use development server that comes with django
There is a testing server (apache) that runs somewhere else, and everytime i finish something I need to manually copy my work via WinSCP/Putty and make sure it works on testing server
Testing server is accessible for our testers to use and test and report bugs
I would like to automate this process as it is very painful. It involves me to export the whole repository, copy to the testing server, get rid of the pyc files, sometimes restarting apache, use the correct settings.py (usually some renaming).
I would like to for the testing server to automatically retrieve new files after each SVN commit. I could write a custom script to do all this stuff, but something tells me that there are some easy-to-use solutions I could use to change my workflow to make things less painful.
One extra bonus. There is a designer that works on HTML/CSS on the templates directly on the testing server. I need to check whether he made changes and I transfer them to my computer and subsequently to SVN rep. My boss thinks it's too dangerous to give him SVN access. Any ideas to help me out with this, also?
deployment:
I would say its better to do the deployment the same way you do for the production. Fabric is a good solution.
SVN way:
If you want to do it in the SVN way, create a branch called testing, once you have a working version of your code and ready for testing merge the development branch to the testing branch. Make sure you have permission on the testing branch to restrict everyone from merging to the test branch. After merging the test team should take a update to a specific version.
.pyc
It unnecessary to manually remove pyc files you can add a svn hook which can ignore the pyc files on commit. Create a file .svnignore
*.pyc
and run this command
svn -R propset svn:ignore -F .svnignore .
If you’ve already got yourself into the mess of versioning your compiled files, then you can do either of these things.
find -name "*.pyc" -exec svn revert {} \;
find -name "*.pyc" -exec svn delete {} \;
Django settings file
You can set the environment variable through which django can take up corresponding settings file. Django set env
Designer
well designer working directly on the test server is not a bonus point. :) its a headache. In a ideal environment no one should touch the code in the testing server. Create a separate branch for the designer or he can commit to the dev branch which all the developers can merge.
One option is to create a read only svn user and have it checkout the svn repository on the apache server. Then to do a build you run 'svn update'. You can check if the designer modified files by doing a 'svn status'.
If your svn repository is on the same machine as your qa django instance you could use a post-commit hook to have it svn update after each commit, and bounce apache if needed. See http://subversion.tigris.org/faq.html#website-auto-update