Skip to content

don't render empty list element in ce (#4596) #1

don't render empty list element in ce (#4596)

don't render empty list element in ce (#4596) #1

Triggered via push September 20, 2024 20:34
Status Success
Total duration 9m 23s
Artifacts

elixir.yml

on: push
Static checks (format, credo, dialyzer)
9m 11s
Static checks (format, credo, dialyzer)
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

25 warnings
Build and test (ce_test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (ce_test, postgres:16)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (ce_test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (ce_test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (ce_test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:15)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Static checks (format, credo, dialyzer)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Static checks (format, credo, dialyzer)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Static checks (format, credo, dialyzer)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Static checks (format, credo, dialyzer)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Static checks (format, credo, dialyzer)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it