We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just updated to Realm 0.95 and am receiving the following build warnings...
../RealmSwift/RealmConfiguration.swift:135:45: Forced cast from 'Object.Type' to 'AnyClass' always succeeds; did you mean to use 'as'?
../RealmSwift/Migration.swift:73:58: 'defaultPath' was deprecated in * version 1: Use Configuration.defaultConfiguration
../RealmSwift/Realm.swift:636:93: 'defaultPath' was deprecated in * version 1: Use Configuration.defaultConfiguration
A bit ironic. :P
Thanks for fixing the analyzer warning in 0.64. :)
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue, @lionpants! The first warning is fixed in master (see https://github.com/realm/realm-cocoa/blob/35575f1dc3713a2f86f5399953cf645ebc850777/RealmSwift-swift1.2/RealmConfiguration.swift#L135). As for the deprecation warnings, those will be addressed once Realm entirely moves from the old path methods to the new configuration methods, which we intend to do for our next major release.
Sorry, something went wrong.
jpsim
No branches or pull requests
Just updated to Realm 0.95 and am receiving the following build warnings...
../RealmSwift/RealmConfiguration.swift:135:45: Forced cast from 'Object.Type' to 'AnyClass' always succeeds; did you mean to use 'as'?
../RealmSwift/Migration.swift:73:58: 'defaultPath' was deprecated in * version 1: Use Configuration.defaultConfiguration
../RealmSwift/Realm.swift:636:93: 'defaultPath' was deprecated in * version 1: Use Configuration.defaultConfiguration
A bit ironic. :P
Thanks for fixing the analyzer warning in 0.64. :)
The text was updated successfully, but these errors were encountered: