chore: Reformat AS3 code using asformat #18439
Draft
+16,599
−14,517
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
evilpie
commented
Nov 1, 2024
| public function splitTextElement(elementIndex:int, splitIndex:int):TextElement | ||
| { | ||
| var element = getElementAt(elementIndex); | ||
| if (!(elementinstanceof TextElement)) |
There was a problem hiding this comment.
And it apparently produces wrong code ...
There was a problem hiding this comment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the result of formatting our current AS3 code using the Apache Royale Formatter. To be honest, I'm not a big fan of the result, simply because I don't like it when braces are added to a new line. It also doesn't fit in with our current style.
If we do decide to land this, we could add a CI lint check that ensures all AS3 in pull requests is correctly formatted.