read_glatos_detections coerces to data.table

[mhpob]

Tests for read_glatos_detections currently fail as the "correct" objects (data(walleye_detections) and data(lamprey_detections)) are of the class glatos_detections/data.frame, while importing a csv via read_glatos_detections returns a glatos_detections/data.table/data.frame regardless of input (data.frame, data.table, tibble).

Considering other functions attempt to conserve input class, is this the desired behavior?

[mhpob]

Tests for read_glatos_receivers also fail for a similar reason: data(sample_receivers) is not a data.table.

[chrisholbrook]

This is not the desired behavior; was introduced in v0.8.0.9000 as an unintended consequences of changes to as_glatos_detections and as_glatos_receivers. Fix will be pushed momentarily. Thanks @mhpob for the very helpful poke.

[chrisholbrook]

Fixed in v 0.8.0.9001 (7912d90).

All tests for read_glatos_detections and read_glatos_receivers are now passing; but are still warning that "context() was deprecated in the 3rd edition." see #201

[chrisholbrook]

@mhpob @jdpye Take a quick scan of 7912d90... I only changed a few lines in R/load-read_glatos_detections.r and R/load-read_glatos_receivers.r but git thinks every line was changed. But not in the other two files. Any idea why?

[chrisholbrook]

@mhpob @jdpye After I committed 7912d90, I then did a git pull and see this new "Style code (GHA)" commit (not made locally by me; authored by me on github?

[mhpob]

That's the "style" GH Action that was added with the R CMD check. Takes code and adds spacing, etc. for a consistent style.

It can be turned off by deleting the file at .github/workflows/style.yml

[mhpob]

Just looked -- the stylr action happens after your original commit with a separate commit and so shouldn't affect the original. No idea why git thought you changed everything.