Closed davidjgoss closed 5 months ago
Name | Link |
---|---|
Latest commit | 0938b4c1372499f805d37c18c9acd253fe96db91 |
Latest deploy log | https://app.netlify.com/sites/cucumber-react-components/deploys/65f42e87f4c83e0008909142 |
Deploy Preview | https://deploy-preview-345--cucumber-react-components.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
The "with stacktrace" step fails in the preview with;
TypeError Cannot read properties of null (reading 'type')
at TodosPage.addItem (/Users/somebody/Projects/my-project/support/pages/TodosPage.ts:39:21)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at CustomWorld.<anonymous> (/Users/somebody/Projects/my-project/support/steps/steps.ts:20:5)
@mpkorstanje thats the actual presentation, not an error when trying to render.
Might need some support here as this now means the ruby side renders a shorter message than previously before. All stacktrace data is now missing
Will chat to you later about this @davidjgoss
π€ What's changed?
This PR adds support in the components for an
exception
object within theTestStepResult
. This is designed to give more structured information about a problem than the flat stringmessage
field. We'll now use the exception (and disregard the old message field) if present.β‘οΈ What's your motivation?
Make use of the structured exception object for Cucumber implementations that support it, whilst maintaining backwards-compatibility with those that don't yet.
π·οΈ What kind of change is this?
π Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.