added pep8 check function

[Grashalmbeisser]

No description provided.

[phorward]

Hi!

The purpose of this function is not clear to me. We currently try to distribute a tox.ini file with every project, which also integrates with IDE linters, so that files are checked for PEP8 during editing already.

IMHO, viur-cli should focus on project setup #165, etc. to maintain project files automatically.

[phorward]

Can this definition be used from the tox.ini file provided with the project?

[sveneberth]

The argumentation for or against this is similar as in #160.

IMO the viur-cli doesn't need to implement a CLI command for another software which has already an CLI.

---

I have an alternative suggestion:

Add a corresponding default command to the viur-base's Pipfile, like https://github.com/viur-framework/viur-core/blob/dd0431bc14c2a2b897f2f54de092cac45b0d5e71/Pipfile#L21. At the end is the project logic.
And the CLI then executes defined commands in the project.json as pre-action hooks.

For example:

{
    "//": "[...]",
    "default": {
        "application_name": "myproject-with-hooks",
        "actions": {
            "pre-deploy": [{
                "command": "pipenv run linter",
                "kind": "exec",
            }, {
                "kind": "viur-cli-build",
            }],
            "pre-devserver": [{
                "command": "pipenv run dependency_check",
                "kind": "exec",
            }, {
                "command": "npm run watch",
                "kind": "exec-background",
            }],
        },
    },
    "//": "[...]",
}