As an API package creator, I'd like my tspec to fully describe the 2-way journey from API response to R data and back, so that I can send response objects back to the API.
untibblify() should be fairly robust already, but transform can break it, if it does more than a simple cast. Allow users to specify a function for the reverse operation. If not provided, we'll use default casting (eventually via stbl-style "OK as long as it doesn't lose info" casting), which we'll likely also apply after untransform to be safe.
untibblify()should be fairly robust already, buttransformcan break it, if it does more than a simple cast. Allow users to specify a function for the reverse operation. If not provided, we'll use default casting (eventually via stbl-style "OK as long as it doesn't lose info" casting), which we'll likely also apply after untransform to be safe.