Closed cphaarmeyer closed 1 year ago
I have a look into this.
Previously, the guesser tried to be a bit too smart and required fields to exist often enough in order for it to actually guess an object. This is difficult to get right and rather the user should be able to easily decide that later on. I have a better workflow in mind 😄 PR #174 is a first step towards an improved guessing API.
Now it works. Thanks!
I have a JSON with a lot of implicitly missing values.
tibblify()
errors while guessing the spec. But actually guessing is possible with the internal functionguess_tspec_object_list()
, butis_object_list()
returnsFALSE
. Looks to me like a common enough case to "just work".Created on 2022-11-25 with reprex v2.0.2