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

Fix/694 static analyser issues #1198

Merged
merged 19 commits into from
Nov 3, 2021
Merged

Fix/694 static analyser issues #1198

merged 19 commits into from
Nov 3, 2021

Conversation

maratal
Copy link
Collaborator

@maratal maratal commented Oct 28, 2021

Fixed the most obvious static analyser issues

@maratal maratal self-assigned this Oct 28, 2021
@maratal maratal linked an issue Oct 28, 2021 that may be closed by this pull request
…hQueues constructor has nullable userQueue argument
- nullable for getters for corresponding nullable properties
- removed unnecessary nil check
…ross the library.

Xcode static analyser issue fix: nullable for `observer` property since it needs to be released.
@lawrence-forooghian
Copy link
Collaborator

lawrence-forooghian commented Nov 1, 2021

Hey @maratal – it looks like you're still working on this one (new commits pushed yesterday). Perhaps it would be best to convert it to a draft so that we know when it's truly ready for review? Because I see that @lukasz-szyszkowski has already approved it, but it's changed since he approved it.

@lawrence-forooghian
Copy link
Collaborator

I'm also curious where in Xcode you're seeing these static analyser warnings?

@maratal
Copy link
Collaborator Author

maratal commented Nov 1, 2021

Perhaps it would be best to convert it to a draft so that we know when it's truly ready for review?

It certainly would, but I've finished already =) Now it's ready.

I'm also curious where in Xcode you're seeing these static analyser warnings?

Menu->Product->Analyze

Copy link
Contributor

@QuintinWillison QuintinWillison left a comment

Choose a reason for hiding this comment

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

As discussed in yesterday's in-person call, I would like to see evidence that this is being (or will be) checked in the CI environment (GitHub workflows). I believe that would be one of two options:

  1. Add to this PR a commit that switches on static analyzer when building (RUN_CLANG_STATIC_ANALYZER build setting, I think) - or, perhaps, run xcodebuild analyze from workflow(s)
  2. Create an issue to add this to our backlog - recognising that when we work on that there may be additional transgressions to fix

Copy link
Collaborator

@lawrence-forooghian lawrence-forooghian left a comment

Choose a reason for hiding this comment

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

Looks good – I agree with what @QuintinWillison said about getting this done in CI, too.

@maratal
Copy link
Collaborator Author

maratal commented Nov 2, 2021

I agree too, but I think it should be done in a separate issue. Will do.

@maratal maratal merged commit 3994399 into main Nov 3, 2021
@maratal maratal deleted the fix/694-static-analyzer-issues branch November 3, 2021 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Address issues raised by Xcode’s static analyzer
4 participants