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 No Shadow rule for eslint #87

Merged
merged 2 commits into from
Apr 9, 2024
Merged

Conversation

filip131311
Copy link
Collaborator

@filip131311 filip131311 commented Apr 8, 2024

This PR adds so-shadow rule to enlist, in order to prevent bugs during comparison in nested scopes.
Additionally this PR back fixes all violations of this rule.

Copy link

vercel bot commented Apr 8, 2024

Someone is attempting to deploy this pull request to the software-mansion Team on Vercel.

To accomplish this, the commit author's email address needs to be associated with a GitHub account.

Learn more about how to change the commit author information.

@filip131311 filip131311 merged commit 3c306ef into main Apr 9, 2024
1 of 2 checks passed
@kmagiera kmagiera deleted the @Filip131311/AddNoShadow branch April 9, 2024 14:46
kmagiera added a commit that referenced this pull request Apr 9, 2024
This PR renames launch configuration properties introduced in #90 

It turns out you can use nested objects for launch configuration which
looks much better.

We are renaming fields like "iOS:scheme" to nested structure `ios: {
scheme: "Debug" }}`

This PR also fixes issue introduced in #87 where variables used as
object keys were renamed in WebviewController.ts
filip131311 added a commit that referenced this pull request Apr 15, 2024
This PR adds so-shadow rule to enlist, in order to prevent bugs during
comparison in nested scopes.
Additionally this PR back fixes all violations of this rule.

---------

Co-authored-by: Filip Andrzej Kaminski <[email protected]>
filip131311 pushed a commit that referenced this pull request Apr 15, 2024
This PR renames launch configuration properties introduced in #90 

It turns out you can use nested objects for launch configuration which
looks much better.

We are renaming fields like "iOS:scheme" to nested structure `ios: {
scheme: "Debug" }}`

This PR also fixes issue introduced in #87 where variables used as
object keys were renamed in WebviewController.ts
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.

2 participants