Unhelpful error when there are no new rows

[thomaszwagerman]

During 03_verify_no_past_changes.R, an unhelpful error message is passed to the shell, when no new rows appear.

Error in `error_cnd()`:
! Conditions must have named data fields
Backtrace:
    ▆
 1. ├─butterfly::loupe(current_output, existing_file, datetime_variable = "time")
 2. │ └─butterfly::create_object_list(...)
 3. │   └─cli::cli_abort(...)
 4. │     └─rlang::abort(...)
 5. │       └─rlang::error_cnd(...)
 6. └─rlang::abort(message = message)
Execution halted

An error is the intended behaviour, after all if there are no new rows data transfer does not need to occur. However the cli::abort() message is intended as such:

    cli::cli_abort(
      "There are no new rows. Check '",
      deparse(substitute(df_current)),
      "' is your most recent data, and '",
      deparse(substitute(df_previous)),
      "' is your previous data. If comparing directly, try waldo::compare()."
    )

Ideally this message is fed back to the user.

[thomaszwagerman]

Resolved in latest version of butterfly antarctica/butterfly#27