I propose this topic as feature request, but it's also a documentation issue, as lack of details in user guide paragraph: https://rasa.com/docs/rasa/core/actions/#custom-actions.

What specified in paragraph Execute Actions in Other Code is obscure to me, and details at the API documentation link [Action Server](]https://rasa.com/docs/rasa/api/acti

I have some values in slots that are surrounded by curly braces and are meant to be returned as is. Instead, the trailing brace is being stripped. "${website}" becomes "${website". I have training examples where the whole "${website}" is included. Is there a way to change this behavior?

This is a good first issue and will help new contributors to get familiar with the codebase. Also This issue doesn't aim to add all Metrics to mlpack since each metric would have to be maintained, this aims to add metrics that either I find essential (or have used a couple of time) or those metrics which are very common.
List of metrics that can be added include:

1. IoU and meanIoU

I'm sorry if I missed this functionality, but CLI version hasn't it for sure (I saw the related code only in generate_code_examples.py). I guess it will be very useful to eliminate copy-paste phase, especially for large models.

Of course, piping is a solution, but not for development in Jupyter Notebook, for example.

I run this code

import os
os.environ['is_test_suite']="True" # this is writen due to bug for multiprocessing and pickling I issued. #426 
from auto_ml import Predictor
from auto_ml.utils import get_boston_dataset
from auto_ml.utils_models import load_ml_model

# Load data
df_train, df_test = get_boston_dataset()

# Tell auto_ml which column is 'output'
# Also note columns t

1. installation
2. example csv header table
3. list of available header options

do all of this before explaining the benefits, etc.

showing them what it can do is way more powerful than explaining it.

Feature request

What is the expected behavior?

What is motivation or use case for adding/changing the behavior?

How should this be implemented in your opinion?

Are you willing to work on this yourself?
yes

@JensLehmann @patrickwestphal @SimonBin
In order to have a complete and up-to-date documentation, all available components need to be annotated. For instance, several heuristics do not have an annotation, thus, they do not occur in the current documentation. Moreover, all config options should be described.