Closed nethad closed 9 years ago
Hi @nethad,
I'd like to keep the versions equal to the javascript plugin, so as soon as there's a new version :)
Hmm - it doesn't looks logical. Rails (or sass or something else) can bring some breaking changes and it will make you gem completely broken, but you will sit and wait for js plugin version change :( This is first order rails gem so IMHO should reflect rails changes too.
@webhive this isn't a breaking change, however I just pushed version 3.3.3 with the fix.
My main goal was to reflect the version of the gem with the version of the javascript library, but that was just a thought I'm willing to let go
Thank you for update! I see your naming idea. I just think this is hard or even impossible to reflect version only of one side of gem (js) and ignore other side (rails).
@manuelvanrijn Thank you!
Hi,
do you plan to release a new version for this gem? This would remove the deprecation warnings already fixed in master.