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

compatibility with marginaleffects 0.9.0 #20

Merged
merged 1 commit into from Feb 1, 2023
Merged

compatibility with marginaleffects 0.9.0 #20

merged 1 commit into from Feb 1, 2023

Conversation

vincentarelbundock
Copy link
Contributor

@vincentarelbundock vincentarelbundock commented Feb 1, 2023

Apologies for the trouble, but version 0.9.0 of marginaleffects will break etwfe. Unfortunately, this means that you will receive an email asking you to upload a new version to CRAN very soon.

This PR fixes all compatibility issues I could notice, and makes the tests slightly more resilient to future issues.

One recommendation: avoid using the column name "group" as in test_baker.R. This is a "reserved" word in marginaleffects; I will build some guardrails in the future, but for now this is dangerous.

@grantmcdermott
Copy link
Owner

Merci @vincentarelbundock. Appreciate the heads-up and the proactive fix! Quick question before I merge: Have you submitted to CRAN yet?

@vincentarelbundock
Copy link
Contributor Author

Yes, it's already submitted. Sorry this is so quick. I was pushed to submit by a revdep issue of my own, and didn't think about etwfe.

I'm not used to having people depend on my packages, but I'll try to have a revdep workflow on Github actions so we have more forewarning.

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

Successfully merging this pull request may close these issues.

None yet

2 participants