require_tree 'tada', :autoload, which includes the files in the bundle but does not execute the actual require, so then the
loadcan be resolved later at runtime, just like you would require)
load means the library is reloadable in testing, which is really important for the lexer development flow. is it causing problems?
loadin "production" code to make the library reloadable in testing?
requirebut I don't want to sound like it's a personal preference
I've added a changelog on Asciidoctor.js but dealing with conflicts on almost every single pull request is really annoying
completely agree, in fact lately I'm adding to the UNRELEASED after each PR merge, I do that from the web, it ends up in more commits but except from that works fine
Our initial, boring solution to the problem was to begin adding empty placeholder entries at the beginning of each monthly release cycle. The changelog for the upcoming unreleased version might look like this:
📣 @/all I opened a slack workspace to enable github pull-request reminders and also because of the feature set (vs. gitter looking kinda dead), everyone is welcome to join with this link :link:
The Slack address is https://opalrb.slack.com
I'll still watch gitter notifications if anyone still prefers it, but it's very likely that if everything goes well slack it's gonna be the official chat for Opal