You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it really necessary to depend on magrittr? The pipe syntax seems orthogonal to an API package like gmailr. Should not the user be expected to library(magrittr) when they want access to the alternative syntax? Since the pipe theoretically applies to any API, is every library going to import and export the %>% symbol? That does not seem sustainable.
The text was updated successfully, but these errors were encountered:
I think you are probably right in this case, I don't feel like it adds much to gmailr in practice either, I personally tend to construct the email with one call to gmailr::mime() myself. Also there may be a bug in the generated mail body (#34)
Is it really necessary to depend on magrittr? The pipe syntax seems orthogonal to an API package like gmailr. Should not the user be expected to
library(magrittr)
when they want access to the alternative syntax? Since the pipe theoretically applies to any API, is every library going to import and export the%>%
symbol? That does not seem sustainable.The text was updated successfully, but these errors were encountered: