Go back to rlang::expr_deparse()
except for board_url()
#257
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses these user-reported issues:
vetiver_sm_endpoint()
error "object b not found" #253The change in #241 turned out to actually break generating the plumber files for more complex boards like S3 and similar. 😩
I need to think about testing across different board types in vetiver. The pins package is tested very extensively across all the backends but vetiver does not, and here it is the code that vetiver ran that was the problem. I could probably get away with mocking
vetiver_pin_read()
in such tests to avoid needing to call S3 like pins CI does.