-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
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
Rename Package to remove the _plugin suffix #90
Conversation
b955f26
to
f528a96
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -1,4 +1,4 @@ | |||
import 'package:ably_flutter_plugin/src/spec/spec.dart'; | |||
import 'package:ably_flutter/src/spec/spec.dart'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how I missed this earlier, but linting should have picked up prefer_relative_imports
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be ignored in this PR and I can take it up later. I'll be checking regularly for any linting pointers for every commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, in upcoming PR's we are capturing these lint pointers in workflows: https://github.com/ably/ably-flutter/blob/b917e0e86fdd5d575b3ab2b57d0646580d00992f/.github/workflows/flutter_integration.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just checked, it is fixed in another branch already: https://github.com/ably/ably-flutter/blob/feature/realtime-presence-get-history/lib/src/spec/common.dart
We'll land this pull request before #89.
As discussed in Slack, I'm also going to create a private fork of this repository so we can push a discontinuation to the current package. Clearly that falls outside of the scope of this pull request.