Closed mhpob closed 6 months ago
Yeah; this is a known infelicity of the current way I return everything as a single tibble; we can't merge factors (ordered or otherwise) with different levels and wouldn't want to anyway.
I think I really want to return a nested tibble with 1 row per effect (1 row for each smooth or parametric effect), which will allow for storage of the levels as we won't need to convert them to character to bind all the effects together. But that would be quite a change to the UI and would fail as soon as someone unnested the tibble...
Right now, the best I can think of is to attach another attribute the carries the factor levels in a list, and make sure I preserve that attribute through any subsetting operations.
This is now fixed in the devel version on GitHub. I'll make a release to CRAN shortly after June 10th.
Everything evaluates fine, but the terms are not ordered after
parametric_effects
and plotted in alphabetical order.The factor and its ordering look to become purposefully uncoupled into row order, an "ordered" type, and an unordered character representation of the levels in
parametric_effects
. The row ordering is not passed on to the base plotting step ofdraw_parametric_effect
.