it is not described what data and how generated
for blackbox lime:
https://eli5.readthedocs.io/en/latest/blackbox/lime.html
eli5 supports dataset generation using Kernel Density Estimation, to ensure that generated dataset looks similar to the original dataset;

1
can you generate dependency in data when data is mixture on categorical and continues variables
for example
feature 1: green,

We're using Scapegoat 3.11. When running:

gradle build

It runs compileScala and compileTestScala, (among other tasks) and both of these are of type ScalaCompile. The documentation specifies that we should use:

tasks.withType(ScalaCompile) {
  scalaCompileOptions.additionalParameters = [
    "-Xplugin:" + configurations.scalaCompilerPlugin.asPath,
    "-P:scapegoat:da

Hi,
in the cli there are this options:

• --checks
• --error-limit
• --infer-schema/--no-infer-schema
• --json
• --order-fields
• --output
• --preset
• --quiet
• --row-limit
• --schema
• --skip-checks
• --table-limit

But I do not find any documentation here and if I write goodtables --help I have only the text below.

I could try to help with a PR, reading the cli.py code.

Thanks for this plugin, in the first place 👍

I would like to use the text search feature inside the table view. (And ideally also the replace functionality, but this could be a separate ticket.)

Currently, Ctrl-F only works in the text part but not in the table editor. It would be nice if that feature could be added to the table editor as well.

As a first step it would be good if the

As shown in the following examples:

>>> ls(os, 'blah')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/skeledrew/.pyenv/versions/3.6.1/envs/general/lib/python3.6/site-packages/python_ls/_ls.py", line 32, in ls
    dunder=dunder, under=under):
  File "/home/skeledrew/.pyenv/versions/3.6.1/envs/general/lib/python3.6/site-packages/python_ls/_ls.py",

In the Predicates section:

Notice: like in Mulang means that it contains that case-insensitive substring

I think this could be better explained by emphasizing the use of ~ like in the second example here

See mumuki/mulang#260 comment

Users should be able to hover a ? hint and see a description of the annotation.

Implement this for the BASE_STYLE annotation.

The inspection tries to determine if the class is singleton by presence of getInstance methods but I noticed a lot of false positives.

When applying a default annotation to package scope should remove redundant default annotations in the same package.

For example a class annotated with @NonnullByDefault, or @ParamsAreNonnullByDefault in the same package where a @NonnullByDefault annotation gets applied to package-info.class.

Or a package-info.java which already has @ParamsAreNonnullByDefault but now gets @NonnullByDefault a