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

Remove tidyr::spread() #552

Merged
merged 5 commits into from
Jul 11, 2023
Merged

Remove tidyr::spread() #552

merged 5 commits into from
Jul 11, 2023

Conversation

olivroy
Copy link
Contributor

@olivroy olivroy commented Jun 19, 2023

Description

Removing mentions of the superseded tidyr functions.

Related Issue

Addresses #549

R/tabyl.R Outdated Show resolved Hide resolved
@codecov
Copy link

codecov bot commented Jun 19, 2023

Codecov Report

Merging #552 (73fd5f5) into main (4574e25) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##              main      #552   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           26        26           
  Lines         1179      1183    +4     
=========================================
+ Hits          1179      1183    +4     
Impacted Files Coverage Δ
R/adorn_title.R 100.00% <ø> (ø)
R/tabyl.R 100.00% <100.00%> (ø)

@olivroy olivroy mentioned this pull request Jun 19, 2023
9 tasks
@sfirke
Copy link
Owner

sfirke commented Jul 11, 2023

Excellent! Thank you for commenting the most complex section. And nice job catching the instance of "spread" that is in a comment, not code 😁

@sfirke sfirke requested review from sfirke and removed request for sfirke July 11, 2023 13:42
@sfirke sfirke merged commit 7375941 into sfirke:main Jul 11, 2023
9 checks passed
@sfirke
Copy link
Owner

sfirke commented Jul 11, 2023

BTW did the auto-linter run catch the whitespaces that prompted your last commit?

@olivroy
Copy link
Contributor Author

olivroy commented Jul 11, 2023

Hi, sfirke, it did, in the sense that I get a notification that the style action didn't pass. See #549 (comment)

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