The rule W391 (There should be one, and only one, blank line at the end of each file) is correctly applied when there is no trailing line or exactly one trailing line at the end of the file.

But when there are 2 or more trailing lines, Black leaves 2 trailing lines at the end of the document instead of 1.

Operating system: Ubuntu 18.04
Python version: 3.6
Black version:
Does also happe

If we use Spring MVC there is also something we can add in the model if we use Spring WebFlow. According to Spring Documentation and this SO article this is possible to specific bind the model.

I think this

Add a new array to config file specifying to minimum requirements.

Details

Right now the min requirements can only be supplied as running arguments, however as the same values are often required for these, I think they should be added to the config file.

Our Configuration class should

When working on a fix for #2755 I noticed that tags are being handled that cannot be used anyway, e.g. tags of disconnected changesets. Similarly, per-branch tags should be constrained to the checked out branch.

Skimming through the new comparison between tools, I noticed how all of them use the visually noisy hyphen ----- lines. The box drawing characters could be used to have clean, uninterrupted lines. These improve aesthetics and improve readability.
Of course, this requires unicode support. I wasn't sure if the choice of hyphens was deliberate

https://devexpress.github.io/testcafe/documentation/getting-started/

1. add test:e2e script to package.json which runs testcafe for tests/e2e dir (create dir as well); tests should be run against codedrumbs running at PLAYGROUND_URL (set env var as localhost in webpack.dev config)
2. add page-objects dir in tests/e2e/, put files with selectors there (ID-s for UI controls as well as

Since the default output is meant to be human-readable, would it make sense to add thousands separators to make the output more easily readable?

This is to help people that for whatever reason don't want to go through the effort of changing it manually every time.

Default levels of understanding and thoroughness for both positive (review)and negative(flag) could also be configurable in the user-config file.

Please add C# syntax support.

So that it's easier/possible to print more nicely to the terminal.

When there's no comment, extractlocstrings will generate entries like
/* No comment provided by engineer. */ all over the place. These comments should be removed by default on normalization. There might even be an option to remove comments alltogether.

Hi everyone!

I need help to migrate and refactor the codebase from Vue CLI 2 to Vue CLI 4.

Thanks a lot in advance for your help ❤️