Closed SimonDarksideJ closed 4 years ago
I think we already knew this with all the changes coming down the line. Even more to come.
At this point let's just assume that all existing profiles can be broken at any time unless they're from the sdk directly.
Why mark it as a bug if you feel like it's not worth the effort of supporting backwards compatibility?
I'm going to close this as adding the Breaking Changes labels to the PRs likely means that profiles need to be regenerated. Let's just assume that we will be doing this until version 1.x
XRTK - Mixed Reality Toolkit Bug Report
Describe the bug
Updated Core and SDK for XRTK, this broken existing local Controller Mapping profiles
To Reproduce
Scope
Documentation update
Expectation
Considering the scope of profiles, I feel this just a documentation fix/note for an upgrade, that existing profiles need to be re-cloned and configured. Rather than effort to resolve the backwards compatibility