Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Specifications and type for failure reasons

See original GitHub issue

Hi Lutando, I’m seeing that the “errors” parameter for the FailedExecutionResult has changed from an IEnumerable<string> to string[]. However, the type returned from WhyIsNotSatisfiedBy(T obj) in the Specification<T> class remains IEnumerable<string>. It is requiring that we now add “.ToArray( )” to our calls. Was this intentional?

... new FailedExecutionResult(ourSpecification.WhyIsNotSatisfiedBy(command).ToArray());

Not a major issue, I think.

Issue Analytics

State:
Created 4 years ago
Comments:12 (5 by maintainers)

Top GitHub Comments

1reaction

Lutandocommented, May 15, 2019

this has been fixed in 0.4.5 😃

1reaction

Lutandocommented, May 6, 2019

Maybe I can find out why tomorrow 😁

Top Results From Across the Web

Product Specifications and Failure

Having such specifications would provide a valuable reference guide should a product fail in service, helping the analyst determine whether the failure was ......

Chapter 3. Failures and Failure Classification

An item can fail in many di erent ways – a failure mode is a description of a possible state of the item...

Failure cause

Failure causes are defects in design, process, quality, or part application, which are the underlying cause of a failure or which initiate a...

Failure Analysis - an overview

Failure analysis is the science and technique of understanding how materials and products fail. Whenever a component no longer performs its intended function, ......

Systematic Failure - an overview | ScienceDirect Topics

Over the last 30 years, increased complexity at both system and component level has led to a raft of failures (known as systematic)...