One thing that occurred to me after making the example: I suspect many of the previous questions about limiting "too many" categorical labels would probably be fine with keeping the ticks, and only thinning the labels. However, these two things are currently implicitly linked. In the example I did save the original ticker on the grid, so that all the grid lines do show up. This seems like it would be a reasonable compromise for most cases IMO, but we can consider splitting off a separate optional labels_ticker in the future if it really seems needed.

@mattpap are you done commenting on this PR (and the other one)?

@mattpap I would like to merge this, do you have any comments?

I would mark the new model as experimental

It would strike me as an extremely odd incongruity to mark an API that is identical to all other existing "CustomJS" models as experimental. We are going to have to go through them all in any case, so I don't see the value in manufacturing a special case. FWIW my hope for #13994 was to consolidate implementation details, and possibly extend some functionality that only exists in CustomJS to other models, i.e. additive and/or hidden changes.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.