Skip to content
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

Add Linting #128

Open
wants to merge 32 commits into
base: develop
Choose a base branch
from
Open

Add Linting #128

wants to merge 32 commits into from

Conversation

Leptopoda
Copy link

@Leptopoda Leptopoda commented Oct 6, 2022

Hi there,
I've added linting using the lint package. The package enables all lints available to flutter (all linting rules are still maintained by the flutter team but they them self consider some as less important or not worth enabling on existing projects) so it is a bit strict. I've also fixed the code style to adapt to the lints and most of the lints I touched would also be in the not so strict flutter_lints package which is maintained by the flutter team itself and also enabled on every new project.

Those lints include code style, formatting style removing of unused variables, code flow cleanup ...
In general those lints improve the code readability and performance of the code (some of the stuff the linter points out should be done by the compiler/optimizer anyways but some aren't an example that isn't touched by the compiler is using StringBuffer to compose strings).

@Leptopoda Leptopoda changed the title Add Linting [DRAFT]: Add Linting Oct 6, 2022
@Leptopoda Leptopoda marked this pull request as draft October 6, 2022 16:06
@Leptopoda Leptopoda force-pushed the linting branch 6 times, most recently from 2c75494 to 84c7233 Compare October 14, 2022 09:15
@Leptopoda Leptopoda changed the title [DRAFT]: Add Linting Add Linting Oct 14, 2022
@Leptopoda Leptopoda marked this pull request as ready for review October 14, 2022 09:19
Comment on lines 45 to 53
if (result != null && result is! ScheduleQueryResult) {
// TODO: [Leptopoda] validate changes
if (result == null || result is! ScheduleQueryResult) {
potentialException = ScheduleQueryFailedException(result);
completer.complete(null);
completer.complete();
} else {
completer.complete(result);
}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only changed the logic here but it didn't really make sense the other way around.
Please verify that this is still the wanted implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant