Alternately, if you're not going involve the health department early on so they can help you make it work, don't go to them at all and hope that nobody notices. Getting on their radar when there's no way you can possibly satisfy them is a bad idea. #NotALawyer #NotYourLawyer #NotLegalAdvice
Feel kind of sad for this guy who just came in. He's planning an event but waited way too long to run the food related parts of those plans past the health department and now there's no way he's going to be able to get the right permits on such a short time table. He needed to be partnering with a licensed business a lot earlier so they could navigate getting the off site permit. Food safety is no joke.
@chest_bot open chest
@NorthRiver I've opened an issue to track this so I don't forget about the request. https://code.typica.us/neal/Typica/issues/16
@NorthRiver Right now there's no such feature in Typica and I'm not sure where the best place to fit something like that into the interface might be. Let me think about it for a little while.
As a first thought I think it's more likely that this would get exposed as a way to duplicate a scheduled batch (maybe tucked away in a menu) rather than a field that's very visible for everybody that most people would just leave at 1.
Failed to fix a bug, but in doing so I found lots of bug tracker discussions rejecting patches to upstream introducing APIs that would have at least given me other workarounds to try. I was planning on getting rid of that dependency for 2.0 anyway so now I have another reason to do that. The down side: replacing this is going to be a ton of work.
@deadsuperhero The Mac at the shop is slightly too old a model for the latest release for no good reason.
Author of Typica software for coffee roasters.