Closed jasonknebel closed 4 years ago
The ruby version conflicts were resolved by upgrading rubocop.
The JSON error was part of a long chain. It seems to come from a blank file name on initialization being passed around. I have made changed in the code to get it working again. I will make sure it is the proper implementation and tested. Likely, I'll have a PR for this small fix.
Ignore me. Just needed to upgrade Rubocop. Sorry for the unneeded notifications!
When trying to upgrade to ruby 2.6, I encounter the following error immediately upon boot up of guard.
This seems to come from a change in how
JSON.parse
handles empty values.