Right now, SVG paths are just taken as is. There can be all sorts of nasty bugs hiding in there! One such bug, is when the end point equals the start point.
Technically, this should be fine. But some of the math ends up degenerating if this is the case, so we should just make sure that any closed paths implicitly wraparound when it reaches the end. This way no duplicate start/end points are needed and the math should be perfect (ha yea right).
Anyways, search the code for this string %BW7n4C2kfxQtpij6tHL to find the area that needs to be cleaned up.
Right now, SVG paths are just taken as is. There can be all sorts of nasty bugs hiding in there! One such bug, is when the end point equals the start point.
Technically, this should be fine. But some of the math ends up degenerating if this is the case, so we should just make sure that any closed paths implicitly wraparound when it reaches the end. This way no duplicate start/end points are needed and the math should be perfect (ha yea right).
Anyways, search the code for this string
%BW7n4C2kfxQtpij6tHLto find the area that needs to be cleaned up.