Right now we can create custom configuration based on presets, however I think it would be worth allowing custom presets also.
This would mean opening up the Preset interface so for example a framework could maintain their own Preset file and users can then use the preset, just by pointing

I did a quick search of the issues, both open and closed, but didn't see something like what I'm proposing.

The problem I am having is that reek is throwing up warnings for scaffolding code that hasn't yet been fleshed out. I've included an example below.

I'd like a mechanism that will let me suppress all warnings for a function in the particular instance that the function is not yet impleme

https://github.com/codeclimate/codeclimate/blob/18c2509474b0bdadad1174559257661a75131818/codeclimate-wrapper#L114

https://docs.docker.com/docker-for-mac/osxfs-caching/

it seems that adding :cached to the /code, config, and cached volumes and :delegated to the /tmp/cc volume may improve performance on OSX machines at least.

Hello,

in the moment i test PhpMetrics.
I use PhpStorm with the PhpMetrics - Plugin.
I will write my own config file for PhpMetrics.
For example i have a ' .phpmetrics.yml ' file under the document root of my project.

I will change the measure for the maintainability index.
--------------------- .phpmetrics.yml ----

default:
rules:
cyclomaticComplexity: [ 10, 6, 2 ]

fastp will overwrite -o without checking if it is the same as -i. Worth adding a check for this scenario.

Right now the tutorial uses WAY more detail than would actually be used in a project. To avoid pushing users into a pitfall of over-specifying their project I need to be more upfront in the docs that the highly specific nature is for demonstration, but not a representation of how an actual project would be specified.

Currently the runner creates an empty files in docs/ when there is no @public in the JSDoc comment (e.g. or no comments at all in the .js file).

In Qulice 0.18.19, If I have this code:

    /**
     * constructor.
     * @param add {@link FieldAddition}
     * @param mul Field multiplication
     */
    public AbstractField(final FieldAddition<T> add,
        final FieldMultiplication<T> mul) {
        this.add = add;
        this.mult = mul;
    }

Qulice will complain with 2 violations:

• `First sentence in a comm

The puzzle 452-fc6e85e0 from #452 has to be resolved:

https://github.com/yegor256/jpeek/blob/ab8826a691bab7f18cde3c717e5f03575781fcfd/README.md#L48-L50

The puzzle was created by paulodamaso on 21-Apr-20.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the pu

Support jUnit XML properties in the already existing extension.
The properties should origin from the Feature Description like:

Feature: XML Properties
    This is arbitrary text and shouldn't be treated as
    a property. Even with a colon in it.

    Property A: foo
    Property B: bla

Also see #387

Even your README.md has a broken badge in the README. I have seen suggestions to work around this with an anchor, '#.svg', but that doesn't seem to work anymore either.

First of all, thank you for making this tool!
I tried it today, and saw that the excel report could be improved with data already present in the docx report

Expected behavior

The excel report includes summary metrics, such as

and

  | Cyclomatic Complexity | Cognitive