You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
teraz mame pre txm event attribut s nazvom strictness_type. zatial sa to lisi v tom, ako sa filtruju active_and_valid_donors_dict a active_and_valid_recipients_dict, a este v tom, na akej urovni sa vracaju ktore parsing issues v get_messages, no toto je len provizorne nakodene.
chcelo by to byt urobene tak, ze sa uroven parsing issues uz rovno bude odvijat od typu strictness_type, cize by get_messages nemali byt zmenene, ale txm event by mohol (priklad) mat nieco ako info o tom, kam patri aky typ parsing issue pre ktory strictness typ.
taktiez by to malo vyriesit to, aby sa tam dali lahko pridat nove urovne bez nejakej obskurnej zmeny v kode, a lahko dalo menit aj to, ze napr konkretny typ parsing issue bude zakazany napr aj v tom FORGIVING strictness type.
The text was updated successfully, but these errors were encountered:
teraz mame pre txm event attribut s nazvom
strictness_type
. zatial sa to lisi v tom, ako sa filtrujuactive_and_valid_donors_dict
aactive_and_valid_recipients_dict
, a este v tom, na akej urovni sa vracaju ktore parsing issues vget_messages
, no toto je len provizorne nakodene.chcelo by to byt urobene tak, ze sa uroven parsing issues uz rovno bude odvijat od typu
strictness_type
, cize byget_messages
nemali byt zmenene, ale txm event by mohol (priklad) mat nieco ako info o tom, kam patri aky typ parsing issue pre ktory strictness typ.taktiez by to malo vyriesit to, aby sa tam dali lahko pridat nove urovne bez nejakej obskurnej zmeny v kode, a lahko dalo menit aj to, ze napr konkretny typ parsing issue bude zakazany napr aj v tom FORGIVING strictness type.
The text was updated successfully, but these errors were encountered: