Closed thomaszwagerman closed 2 years ago
Looking at this again and had a thought.
I've replaced pin_created()
with a function called pin_hash()
, however where pin_meta()
returns $created
for the date the pin was created, for the hash of the pin contents it returns $pin_hash
. When I looked back over the code this caused confusion.
Either I change the pin_hash()
function name, or the output of pin_meta()
should be changed from $pin_hash
-> $hash
, which I think is more consistent with the rest of pin_meta()
's outputs.
Thank you so much for this PR @thomaszwagerman and for your patience on it!
I agree that it's not ideal that the hash is called pin_hash
in the pin metadata. However, it wouldn't really solve this specific question because there is an existing unexported function called pin_hash()
:
Even if we were to change the name of pin_hash
, we still need to change the function name here. Maybe get_pin_hash()
?
Hi @juliasilge, thank you for you reply, and no worries at all for the wait!
Apologies, I was not aware of the unexported pin_hash()
- I've implemented your suggestion by changing the function name to get_pin_hash()
.
This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
Replaces
pin_created()
withpin_hash()
, which supports functionality ofpin_reactive_read()
andpin_reactive_download()
.Suggestion made by @TylerGrantSmith.
Closes #542