@@ -10,7 +10,27 @@ Documentation:
10
10
When an element returns None, subsequent
11
11
elements are still triggered
12
12
13
- Exceptions:
13
+ Logging:
14
+
15
+ #1 INFO:
16
+ Ordinary debug trace messages
17
+ Can be switched on or off by the user (checkbox in element configuration)
18
+ Implementation in own code is optional
19
+
20
+
21
+ #2 WARNING:
22
+ Signalize a failed execution
23
+ Can be switched on or off by the user (checkbox in element configuration)
24
+ A log entry of this type is created when the element returns data of type PythonicError
25
+ Implementation in own code is optional
26
+
27
+ #3 Critical (Unhandled exception):
28
+ Is signalized in the GUI an (,,Exception occured, open log for details)
29
+ Log entry (type ERROR) is made
30
+ Is always active (implementation not optional)
31
+
32
+
33
+ Error handling:
14
34
15
35
#1
16
36
Elements should throw an exception when configuration
@@ -21,16 +41,19 @@ Documentation:
21
41
and only throw critical exceptions.
22
42
23
43
#3
24
- If appropriate, the result of a operation (if successfull or not) should
25
- be forwarded to subsequent elements in order to react to
26
- a possible unsuccesfull operation. When it was not possible to process the input data, return the PythonicError with related information.
27
- Combine this with logging.warning (preferred) or logging.error .
44
+ The result of a operation (if successfull or not (see #2)) should always
45
+ be forwarded to subsequent elements in order to react to a possible failed call.
46
+ If the result of a failed call could be processed by an subsequent element,
47
+ it should be wrapped inside the PythonicError type .
28
48
29
49
#4
30
- Avoid to use logging.error or logging.warning without the other mechanisms as those methods will only write to the log.
50
+ In case of a failed call, a meaningful message or the exception text should returned
51
+ (PythonicError as data parameter in returned Record type)
31
52
53
+ #4
54
+ Dont to use logging.error or logging.warning as it has no effect if used in combination with multiprocessing.
32
55
33
- Check exception rules
56
+ 1917141915:AAHRe-CZhv8fIv6bQzHMipgYPuVnQbQGxtY
34
57
35
58
CCXT Method: Try to optimize large if-else areas for parsing config
36
59
0 commit comments