question-mark
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.

Feature Request: updated `.fixture` diffing

See original GitHub issue

The current output of assert.fixture(formatted,out) isn’t very intelligible to me currently: image

I ended up just printing out the values side by side so I could actually see the difference in formatting between them…

Would it be possible to use a more advanced diffing output that looks similar to delta?

example: image

It’d be nice if it was possible to just use delta, but it’s written in rust and I doubt they publish a WASM npm package.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
lukeedcommented, Aug 5, 2021

I’d consider highlighting the whitespace difference. I mean, to me, it’s pretty clear that one is more indented than the other, but highlighting could help in some cases perhaps.

Fwiw, jest has the same whitespace display as I do (no highlight) and some would say that’s the expectation/standard now.

Closing as duplicate of #1 as in general that ticket is about more control over diffing.

Thanks 😃

1reaction
lukeedcommented, Aug 4, 2021

I looked at relying on a delta installation already being installed on the host machine, but it wasn’t a good idea in terms of practicality. It would have also made uvu the only JS test runner to have a non-JS system peer dependency… and either at that point, or with a WASM integration, you start dancing around the “why use JS at all” question/territory.

That aside, the two screen shots you have are saying the exact same thing. The only real difference is that uvu’s is using text color while delta’s is highlighting the line with red/green backgrounds.

The other diff difference is that uvu detected missing new lines before the <style> tag & the other one doesn’t. My guess is that you/something compensated for that as part of creating the formatted-rename-me.astro file creation

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Submit a New Feature Request - Vagaro Support
How to Submit a New Feature Request · 1.png. -OR- From any place in your Vagaro web application, click the Help icon (...
Read more >
Difference Between a Bug or a Feature Request - Kualitee
According to software engineers, the difference between a bug and a feature request is super clear. A bug/defect/issue is any erroneous.
Read more >
107006 - Feature request: ability to replay a previously made ...
When developing applications I'm updating json files stored locally and those changes are not detected by Chrome. As a result the modifications are...
Read more >
How to Manage Product Feature Requests – 6 Best Practices
Easy fix: put all your product feature requests into one place like a project management tool, where you can visualize, prioritize, and update...
Read more >
7 Feature Request Tools To Collect & Organize Feedback
However, there are a lot of different feature request tools out there, ... connect in importance and impact to compare features effectively.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found