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

chore: fix some typos in comments #15991

Merged
merged 1 commit into from
Apr 16, 2024
Merged

Conversation

StevenMia
Copy link
Contributor

No description provided.

core/src/avm2/scope.rs Outdated Show resolved Hide resolved
@turicfr
Copy link
Contributor

turicfr commented Apr 15, 2024

I came across many typos in the codebase. A wider approach like the typos crate might help here.

@torokati44
Copy link
Member

torokati44 commented Apr 15, 2024

That has been done before already:
#14803
#15303

But it shows a lot of false positives, a lot of typos that we intend to keep, and a few that are in test SWF sources1, which is not necessarily worth fixing.

Footnotes

  1. Such as: https://github.com/ruffle-rs/ruffle/blob/177a5a6de730aa6da9920e3970ffac88e545e9ea/tests/tests/swfs/avm2/displayobject_invalid_floats/Test.as#L12

@@ -1343,7 +1343,7 @@ pub fn to_xml_string<'gc>(
.get_public_property("prettyIndent", activation)
.expect("prettyIndent should be set")
.coerce_to_i32(activation)
.expect("shouldnt error");
.expect("shouldn't error");
Copy link
Member

Choose a reason for hiding this comment

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

This one is not in a comment, but oh well... :)

Copy link
Member

@torokati44 torokati44 left a comment

Choose a reason for hiding this comment

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

Thank you!

Signed-off-by: StevenMia <flite@foxmail.com>
@torokati44 torokati44 merged commit 899c0bb into ruffle-rs:master Apr 16, 2024
17 checks passed
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.

None yet

4 participants