tgbugs / idlib / 50

60%

push

travis-ci

ror api deal with http 200 returning errors

related to the previous commit, one way to deal with remote errors is
to include in the spec for the behavior of the local data
representation a variant that always succeeds, this means that we need
to move away from using properties entirely, because none of those
properties are guranteed not to produce errors unless instances can
fail to construct, for most applications, the "error free" path needs
to have a separate name because failures will be quieter, though they
should have some data representation, they merely defer the issue, but
being able to collect errors that aren't actually fatal that occur all
over the execution graph and then reveiw them all in bulk is a much
more efficient approach in nearly all cases, the issue is that any
error can currently be fatal or non-fatal depending on context and
whether the calling scope even knows that it could be raised under
certain circumstances

11 of 11 new or added lines in 1 file covered. (100.0%)

949 of 1579 relevant lines covered (60.1%)

0.6 hits per line