add_shape(NULL, NULL) now throws ERROR about rayvertex HOT 3 CLOSED

There was no behavior to deal with NULLs before, but try the latest commit: it should handle NULLs by returning the non-NULL object (or by returning NULL if both are NULL.

from rayvertex.

There was no behavior to deal with NULLs before

In the previous CRAN release v0.3.3 (6930a88) add_shape(NULL, NULL) would return NULL but this very well could have been an accidental unplanned behavior.

try the latest commit: it should handle NULLs by returning the non-NULL object (or by returning NULL if both are NULL

I'm observing that add_shape(NULL, NULL) now returns NULL as it did in v0.3.3 but that scene_from_list(list(NULL, NULL)) now throws an error (which it didn't in the last CRAN release v0.4.11):

scene_from_list(list(NULL, NULL))

Error in do.call(rbind, old_scene$vertices) : 
  second argument must be a list

from rayvertex.

One possible solution may be to filter the scene_list in scene_from_list() using Filter(Negate(is.null), scene_list)

from rayvertex.