Upgrade to the newest bondagejs #6451
Comments
|
btw one added extra of this branch is that the library's deployment size has considerably been shrunk |
|
That seems like a great idea! As usual I would say the most important is to triple check any potential breaking changes/regressions. |
|
yes ofcourse, it may be a case that the wrapper i wrote for it might need some subtle tweaks. It will need to be tested with all the example projects and work exactly the same on them. Bondagejs itself has lots of unit tests - even more on this branch |
|
I made a quick stab at it here, but am having some issues importing the module The strange thing is that it logs the module - so it must have imported it, but gdevelop complains about some end of line error. I can do direct commits to that 2.0 branch btw, so any ideas of how it could be addressed at bondagejs tracker are also welcome :) @mnbroatch trying to ugrade gdevelop to use your upgraded version of bondage |
Description
The current version of bondagejs which gdevelop uses doesnt have full yarn 2 syntax compliance.
Things like inline expressions dont work, so for example you cant show variables in text
The player name is ${playerName}Solution suggested
There is a branch of bondagejs that upgrades it to the yarn2 spec
https://github.com/hylyh/bondage.js/tree/2.0
in theory all thats needed is to simply swap out bondagejs with the new one and test it in gdevelop
The text was updated successfully, but these errors were encountered: