Xuan
Xuan
will look into this. Is there any PR available already? Normally I would prefer beta 6 to start the fix
> Xcode 14 beta 3 fixed the issue with `EaseOutBack` closure not resolving types in time. > > So the only issues are the `replaceSubrange` which I linked to a...
ok.. this sucks, @jjatie @danielgindi @pmairoldi thoughts? What would be the appropriate name now?
> > I doubt someone would use both at the same time. This seems to be implemented in swift 5.7 so maybe this could work https://github.com/apple/swift-evolution/blob/main/proposals/0339-module-aliasing-for-disambiguation.md > > I disagree....
> This is a major oversight on Apple's side. Some of their engineers are probably aware that this library exists. > > Now we need some ideas regarding the naming....
then... a vote? Or you could make the call @danielgindi
I have been investigated on this a few months ago. It's possible, however, we need to change how we create the bar rect. Not so hard, but some decent work...
That's what I investigated before, you can try first. I am still looking for other options. in `public func drawDataSet:` of bar chart renderer ``` swift let cornerRadius: CGFloat =...
yeah I don't think it's a great one, especially your bars are very thin
@CoderZyc not merged yet. there is a PR for it.