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 missing geography_id for triads #76

Merged
merged 2 commits into from
Dec 20, 2024

Conversation

dfsnow
Copy link
Member

@dfsnow dfsnow commented Dec 20, 2024

@dfsnow dfsnow marked this pull request as ready for review December 20, 2024 18:04
Copy link
Contributor

@jeancochrane jeancochrane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little uncertain about the direct geography_id assignment, but otherwise this looks fine!

Comment on lines 263 to 267
geography_id = ifelse(
is.na(geography_id) & geography_type == "triad_code",
triad_code,
geography_id
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Question, non-blocking] Isn't this basically what add_triad_code is doing? Also, do we need the geography_type check in add_triad_code too?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops, nice catch. I left this in from an earlier iteration of trying to solve this fix. This is why we code review. Fixed in 89de3ae.

@dfsnow dfsnow merged commit c8bb07c into 2025-assessment-year Dec 20, 2024
4 checks passed
@dfsnow dfsnow deleted the dfsnow/fix-missing-geo-id branch December 20, 2024 23:07
Damonamajor pushed a commit that referenced this pull request Jan 14, 2025
* Fix missing geography_id for triads

* Remove geography_id in mutate()
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