duster/js/test_cases/helpers_gt/README.md

38 lines
1.3 KiB
Markdown
Raw Normal View History

Based on my tests, it appears dust is sorting based on ascii-table values. This also appears to extend to unicode codepoints based on a symbols test.
2020-05-16 19:45:57 +00:00
Greater than follows the same pattern for not rendering when key is omitted or null.
2020-05-16 21:53:57 +00:00
Longer arrays are greater than shorter arrays if all preceding values match.
Theory for comparing arrays: Compare the values, if theres any mismatched types then take the same action you would for non-matching scalar types.
2020-05-16 19:45:57 +00:00
greater than
------------
All comparisons between non-matching types (for example, int vs string) appear to render the else block.
2020-05-16 19:45:57 +00:00
Comparisons between non-scalar types (like arrays) appears to render the else block
2020-05-16 18:15:44 +00:00
2020-05-16 19:45:57 +00:00
greater than or equals to
-------------------------
All comparisons between non-matching types (for example, int vs string) appear to render the main block.
Comparisons between non-scalar types (like arrays) appears to render the main block
less than
---------
All comparisons between non-matching types (for example, int vs string) appear to render the else block.
Comparisons between non-scalar types (like arrays) appears to render the else block
less than or equal to
---------------------
All comparisons between non-matching types (for example, int vs string) appear to render the main block.
Comparisons between non-scalar types (like arrays) appears to render the main block