Small doc improvements to callback documentation
This commit is contained in:
		| @@ -115,7 +115,7 @@ class AwesomeStrategy(IStrategy): | ||||
|             return 'unclog' | ||||
| ``` | ||||
|  | ||||
| See [Dataframe access](#dataframe-access) for more information about dataframe use in strategy callbacks. | ||||
| See [Dataframe access](strategy-advanced.md#dataframe-access) for more information about dataframe use in strategy callbacks. | ||||
|  | ||||
| ## Custom stoploss | ||||
|  | ||||
| @@ -322,7 +322,7 @@ class AwesomeStrategy(IStrategy): | ||||
|         return 1 | ||||
| ``` | ||||
|  | ||||
| See [Dataframe access](#dataframe-access) for more information about dataframe use in strategy callbacks. | ||||
| See [Dataframe access](strategy-advanced.md#dataframe-access) for more information about dataframe use in strategy callbacks. | ||||
|  | ||||
| ### Common helpers for stoploss calculations | ||||
|  | ||||
| @@ -384,9 +384,8 @@ class AwesomeStrategy(IStrategy): | ||||
|  | ||||
| !!! Warning | ||||
|     Modifying entry and exit prices will only work for limit orders. Depending on the price chosen, this can result in a lot of unfilled orders. By default the maximum allowed distance between the current price and the custom price is 2%, this value can be changed in config with the `custom_price_max_distance_ratio` parameter.   | ||||
|  | ||||
| !!! Example | ||||
|     If the new_entryprice is 97, the proposed_rate is 100 and the `custom_price_max_distance_ratio` is set to 2%, The retained valid custom entry price will be 98. | ||||
|     **Example**:   | ||||
|     If the new_entryprice is 97, the proposed_rate is 100 and the `custom_price_max_distance_ratio` is set to 2%, The retained valid custom entry price will be 98, which is 2% below the current (proposed) rate. | ||||
|  | ||||
| !!! Warning "No backtesting support" | ||||
|     Custom entry-prices are currently not supported during backtesting. | ||||
| @@ -485,6 +484,9 @@ class AwesomeStrategy(IStrategy): | ||||
|  | ||||
| ## Bot order confirmation | ||||
|  | ||||
| Confirm trade entry / exits. | ||||
| This are the last methods that will be called before an order is placed. | ||||
|  | ||||
| ### Trade entry (buy order) confirmation | ||||
|  | ||||
| `confirm_trade_entry()` can be used to abort a trade entry at the latest second (maybe because the price is not what we expect). | ||||
|   | ||||
		Reference in New Issue
	
	Block a user