- No pitchfork here, and I'm with "not deprecating all the functions you're used to using," but per the question I asked you in the docs repo, is the long-term goal to change actual usage down the road for users (i.e., will these functions actually be called on the page with their respective ns)? Again, just for my own clarification, since both "yes" and "no" merit their own conversations.
- FYI, added to my TODO list.
You already changed this, but I'm just agreeing:
transform may come off as a distinction without a difference to users (see my first question above).
types as well? If so, yes. If to
cast, I think it makes more sense as a standalone but appreciate the conflict already mentioned twice here.
I was going to suggest
data as well
Hmmm... if not an accepted outlier, does it make sense to group under
operators since it's more like a single if/else statement than an actual ternary? I'm at a loss....
Any time you make things modular/organized/structured, you make this OCD person very happy