Breaking Changes in Rename to React-JUCE #207
nick-thompson
started this conversation in
General
Replies: 2 comments
-
Great! Nothing broken here :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey folks, another update here, I just merged #216 for which the primary breaking change is the rename of the I believe this is the last of the breakage here, and will be updating the docs to reflect the new name next. 🚀 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey all,
I just wanted to highlight a quick heads up that #202 has just merged, which will be the first (and hopefully the worst) in a small series of breaking changes. I wanted to start up a discussion thread to alert any active contributors that this will cause some slight headaches for current work, but we'll restabilize very shortly. #34 is the issue documenting the reasons for the rename, if you want to see the context.
The only immediate change necessary for end users is that after updating to the latest
master
, you'll need to update your submodules again asyoga
has been relocated fromblueprint/yoga
toreact_juce/yoga
, and you'll need to update your CMakeLists or Projucer projects to now refer toreact_juce
instead ofblueprint
. Hopefully that's an easy one, feel free to post here if you're having any issues and I'll help you out.The forthcoming changes will be smaller:
blueprint::
namespace toreactjuce::
cc @JoshMarler @olidacombe @stfufane @jrlanglois @eupston
Beta Was this translation helpful? Give feedback.
All reactions