Closed mustberuss closed 6 years ago
Yes, I looked briefly over these failures. Regarding the unnest_pv_data
test, the issue is the API is serving some of the new data fields (e,g., pct_data
) in a strange format (i.e., one that is not consistent with the other fields). I have opened up an issue with them to fix this (https://github.com/CSSIP-AIR/PatentsView-API/issues/27). Regarding testing cast_pv_data
, went ahead and updated fieldsdf
to show integer instead of int, which fixes the second failing test you mentioned.
I noticed that the Travis job failed after my PR due to the failure of two tests.
Try using assignee_id instead.
The test appears to be reasonable, ie it should work as written. Could the assert that's failing in unnest-pv-data.R be prefaced with an
if(ok_pk != pk)
? I did that locally and the test passed. Or is the test itself coded improperly?It looks like the api's web pages added forprior_sequence and lawyer_sequence as "int" not "integer" on all seven endpoints. As a local hack I added
"int" = as.integer,
in get_cast_fun in cast-pv-data.R and the test passed. Possibly better to handle the int to integer in fieldsdf.R and/or throw an error when a type isn't recognized?Not knowing the right way to fix either problem I didn't push either change.