Apologies in advance, I cannot see how I could produce a minimal working example of this problem...
I'm writing a ELT package and one of the database writing functions that works fine in the normal environment is producing warnings in the testing environment, which uses
dittodb::with_mock_db to simulate the database responses.
I get the following three warnings (with backtrace)
can't be NULL as of tibble 3.0.0.
must have the same length asx
as of tibble 3.0.0.
can't be empty as of tibble 3.0.0.
They are just warnings, so the function is passing the tests.
The problem is I don't know how to debug these warnings, because they only occur when running the test.
The only thing I've managed so far is to suppress the warnings by enclosing the offending function into three (sic!)
But presumably these warnings do require actioning sooner or later, but I don't know how to figure out which part of the code is causing them.