You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Short story: crack is a bad dependency to have. It's basically abandonware. The last official release (2015) uses the safe_yaml gem, which is also abandonware. Note that this has been fixed more than 2 years ago, but they haven't bothered to make a release with that bugfix.
Making releases has basically no cost. Not releasing versions after bugs are fixed is a mistake.
Note also that the same_yaml gem also fixed the issue more than a year ago. But hasn't released it. There's just no excuse in not releasing versions after changes.
The text was updated successfully, but these errors were encountered:
Yeah, makes sense.
It was added at the point of 0.0.1 (aka The Prototype) "just to play with", obviously hard dependency on abandonware is not an acceptable thing.
Probably I'll drop the xml: true feature completely for now.
I'm running into this issue
Short story:
crack
is a bad dependency to have. It's basically abandonware. The last official release (2015) uses thesafe_yaml
gem, which is also abandonware. Note that this has been fixed more than 2 years ago, but they haven't bothered to make a release with that bugfix.Making releases has basically no cost. Not releasing versions after bugs are fixed is a mistake.
Note also that the
same_yaml
gem also fixed the issue more than a year ago. But hasn't released it. There's just no excuse in not releasing versions after changes.The text was updated successfully, but these errors were encountered: