-
-
Notifications
You must be signed in to change notification settings - Fork 4
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 dm's tests #39
Comments
@krlmlr thanks for the issue. I did notice this too for the dm package as I was doing some testing. The breaking change for the genres table is to expand the table a bit. I don't expect to change it that often. But I'm finally doing an update of the data, so I found some extra subgenres that I wanted, hence the breaking change. Happy to make the updates to dm package function. The schema for the genres data is now three columns: film, category, value. Regarding |
I'm also relying on the pixarfilms package for workshop material... How do you feel about creating functions to access the data, instead of exposing the data as package objects? This would allow for an argument to specify the "edition" of the data. Happy to send a PR. |
@krlmlr Ah I see. Mmm creating functions to access the data seems cumbersome imo, especially when as new movies come out, then I'll try to update the data accordingly. But if you have an example of how that looks, I would be curious to see how that's implemented. I've not implemented or seen a solution like that. I'm intrigued. Otherwise, the CRAN version should still have the data with some of the "errors" or particular structures of the data that you should expect. And because I had to set a tag for that release, for your workshops, you can target that particular release if needed. remotes::install_github("erictleung/pixarfilms@v0.2.1") Let me know what you think |
I see, in the dev version, that the
genre
table has changed, and that thepixar_films
table no longer has a missing value. The dm package makes certain assumptions about the structure of the data, and so might other users. Curious to hear your thoughts on how to deal with that.Releasing dm 1.0.11 now, but I can push an update on short notice if needed.
The text was updated successfully, but these errors were encountered: