> Removing the support completely would be nice, but I thought it may make > upgrading too difficult for applications that used symbol splitting > extensively (even though there exists a mostly automated conversion tool: > https://github.com/jeremyevans/sequel-unsplit). By just changing the > default, you could always turn it back on if you want to use it in your > application. >
Well, it's up to you, but FWIW even though I use this feature extensively I wouldn't consider it too burdensome to upgrade, *especially* given that you've got deprecation warnings and an automatic conversion tool. This may be too much work, or architecturally a bad idea, but another option that occurs to me is to make the "old school" behavior available in a plugin instead of core, so that if somebody wants to upgrade to Sequel 5 but not lose this feature they add a new plugin rather than enabling a Sequel core option. In any case, you're a pretty awesome OSS maintainer and you've built some great stuff, so I think I can speak for a great many users of Sequel (and Roda!) and say, in the end, whatever you decide will be fine :) Cheers, Andrew -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
