Erik Onarheim
Erik Onarheim
@nionis Good find, this is definitely undesirable... we didn't think about creative encodings including casing!
@nionis I was noodling on this, I'm thinking about either storing both version of the value and having a separate way of retrieving values, or making value casing configurable in...
@nionis Awesome suggestion, I've pushed up a PR with that and some other tweaks, needs testing before merging but in theory fixes this
@nionis Apologies for the length of time this took me! I'm be cutting new versions of everything very soon
I support this, you thinking like this?  This would definitely be a breaking change for anyone that's implemented a custom system
I agree, I think keeping them as the Collider would be less confusing > Tangentially (this could be its own issue but I figured i'd throw it in here), I...
@mattjennings How do you feel if we defer this a release to v0.31 or RC (whichever is first?)
I'm into this, I'm leaning towards #1 because re-adding systems seems really rough... but on the other hand that's only once?
We'll need to update our custom patch before we can merge this, it'll fail on doc site deploy (which isn't run in this pr)