Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project status? #38

Open
t3h2mas opened this issue Feb 7, 2023 · 4 comments
Open

Project status? #38

t3h2mas opened this issue Feb 7, 2023 · 4 comments

Comments

@t3h2mas
Copy link

t3h2mas commented Feb 7, 2023

👋 Hello! I wanted to express my gratitude for the wonderful contribution you've made by offering this project to the community.

I've been exploring the issues and releases, and I couldn't help but wonder if the project is still being actively maintained. Would you be able to share some information or update us on its status?

Thank you!

@mycargus
Copy link

+1 happy to help contribute if needed

@levinmr
Copy link
Owner

levinmr commented Jan 4, 2024

I do continue to maintain this project, although not as often as I would like.

Some feature ideas that I am considering how to implement:

  • Disable writing snapshots if rspec is being run in CI. (how do we know when the runner is a CI machine is the blocker there)
  • Automatic snapshot file naming so that a string does not have to be provided (to keep feature parity with jest snapshots)

@devshorts
Copy link

@levinmr for CI can we just have a config (like serializers) that we can set to fail if a new snapshot is written. Then we can easily drive it with our own env vars

@dmorgan-fa
Copy link

@levinmr, just a drive-by comment but GitHub Actions set CI=true as a default env var:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants