Closed StoneCypher closed 5 years ago
I would definitely love to see brace updated to the latest ace, it's tough to diagnose issues when the underlying dep is so far behind. react-ace is also suffering as a result and it'd be a lot easier (in theory) to fix their problem here than having them move off brace.
I pinged him on Twitter and he said he'd see to this mid-January
So I think this might be coming soon?
@thlorenz Hey buddy, could you please hit merge?
Hey looks good @StoneCypher , but I'd prefer two things:
So ideally this PR would have ONE commit which bumps the version in the update script and includes the result of running it (changed Ace files).
i don't understand what you mean by "bumps the version in the update script"
I mean please don't change the brace version inside the package.json as I take care of that during the publish step to npm. As in please remove this commit (along with the other ones unrelated to the upgrade).
I have removed the .travis.yml
and regressed the version in package.json
.
I believe that's what I'm supposed to do, but I have a bad flu and I'm stupid when I'm sick
I will reintegrate travis in a followup PR if you say this is what you meant
OK, could you please squash all this into one commit? Basically all we need for this PR are the changes in this commit.
At this point there are tons of commits here including a merge of another PR which I'm not sure about why it is even here. Alternatively open a new PR with just the upgrade related commit and we'll go from there. Thanks.
Oh. Okay
ahaaaa haaaaaaaaaaaa downloading large repos on conference wifi
This PR: