You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using charts in our project and are currently planning to migrate to Swift6. Our project relies on charts to provide charting functionality across our app. We updated our code to this version and encountered issues with compatibility related to Charts.
What did you expect to happen?
We expected Charts to be compatible with Swift6(or have a compatible version or branch) so we could proceed smoothly with our migration without requiring any major refactoring or workaround.
What happened instead?
Upon attempting to update our codebase to Swift 6, we encountered compatibility issues where charts doesn't compile or work as expected. It appears that charts may require updates to align with the new language and compiler changes introduced in Swift 6.
As this is really critical for our project any insights or an estimated timeline would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
What did you do?
We are using charts in our project and are currently planning to migrate to Swift6. Our project relies on charts to provide charting functionality across our app. We updated our code to this version and encountered issues with compatibility related to Charts.
What did you expect to happen?
We expected Charts to be compatible with Swift6(or have a compatible version or branch) so we could proceed smoothly with our migration without requiring any major refactoring or workaround.
What happened instead?
Upon attempting to update our codebase to Swift 6, we encountered compatibility issues where charts doesn't compile or work as expected. It appears that charts may require updates to align with the new language and compiler changes introduced in Swift 6.
As this is really critical for our project any insights or an estimated timeline would be greatly appreciated.
The text was updated successfully, but these errors were encountered: