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 S3263: Rule should not raise when constant field is used in initialization #692

Closed
Evangelink opened this issue Aug 14, 2017 · 0 comments
Assignees
Labels
Type: False Positive Rule IS triggered when it shouldn't be.
Milestone

Comments

@Evangelink
Copy link
Contributor

Repro steps

https://peach.sonarsource.com/project/issues?id=monogame&issues=AVxf8UJUcR1e80dZvvzL&open=AVxf8UJUcR1e80dZvvzL

Expected behavior

No issue is raised in this context.

Actual behavior

Issue is raised.

@Evangelink Evangelink added Area: RSPEC Type: False Positive Rule IS triggered when it shouldn't be. labels Aug 14, 2017
@Evangelink Evangelink added this to the 6.4 milestone Aug 15, 2017
@Evangelink Evangelink self-assigned this Aug 15, 2017
@Evangelink Evangelink changed the title Fix S3263: Rule should not raise when field is not initalized from another field Fix S3263: Rule should not raise when field uses constant from partial Aug 17, 2017
@Evangelink Evangelink removed their assignment Aug 21, 2017
@michalb-sonar michalb-sonar self-assigned this Aug 22, 2017
@michalb-sonar michalb-sonar changed the title Fix S3263: Rule should not raise when field uses constant from partial Fix S3263: Rule should not raise when constant field is used in initialization Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: False Positive Rule IS triggered when it shouldn't be.
Projects
None yet
Development

No branches or pull requests

3 participants