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

Fix max count for subregions #21

Merged
merged 2 commits into from
Jul 30, 2024
Merged

Conversation

ethanwhite
Copy link
Member

This is currently failing for me locally

@ethanwhite ethanwhite force-pushed the subregion-fix branch 2 times, most recently from 2a436ee to 88ece56 Compare July 27, 2024 19:51
This is currently failing for me locally
The use of .data was causing errors due to use of `$` when specifying single column
names not being allowed and likely further down the pipe as well. This removes use
of .data in the section of the code triggerd by level = "subregion".

It also fixes a problem caused by using bind_rows with different named columns
("region" in one table, "subregion" in another table).

The goal was to maintain the behavior of the function as written, but I think
there is also a conversation to be had about how level = "subregion" results in
data source mixing that may be unintuitive to users and should be clearly
documented.
@ethanwhite ethanwhite requested a review from gmyenni July 27, 2024 22:58
@ethanwhite ethanwhite changed the title Add a test for max count for subregions Fix max count for subregions Jul 29, 2024
@gmyenni gmyenni merged commit 6c5c506 into weecology:main Jul 30, 2024
1 check passed
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.

2 participants