Describe the bug
In the JS editor, the is (mySprite) hitting wall (direction) code block turns into text that says mySprite.isHittingTile( ) but we believe it should say mySprite.isHittingWall( ) to match the description on the JS code block and the blocks version of this code.
To Reproduce
Steps to reproduce the behavior:
Go to the JS editor in MakeCode Arcade
In Scene, find the is (mySprite) hitting wall (direction) block, then drag the block out into the coding area
The block turns into the JS text mySprite.isHittingTile( )
The documentation under the code block in the menu, as well as the pop up documentation box, also use the word "tile"
Expected behavior
We expected the word "tile" to be replaced by the word "wall" in the code and the documentation since the code is checking if the sprite is hitting a wall tile
Screenshots
Code block and documentation in the Scene category:
JS code as it appears in the coding area when dragged out:
Desktop (please complete the following information):
OS: Windows
Browser: Chrome
Version 105
Additional context
Please let us know if this behavior is intentional and not a bug @riknoll 😄
Describe the bug In the JS editor, the
is (mySprite) hitting wall (direction)
code block turns into text that saysmySprite.isHittingTile( )
but we believe it should saymySprite.isHittingWall( )
to match the description on the JS code block and the blocks version of this code.To Reproduce Steps to reproduce the behavior:
is (mySprite) hitting wall (direction)
block, then drag the block out into the coding areamySprite.isHittingTile( )
Expected behavior We expected the word "tile" to be replaced by the word "wall" in the code and the documentation since the code is checking if the sprite is hitting a wall tile
Screenshots Code block and documentation in the Scene category:
JS code as it appears in the coding area when dragged out:
Desktop (please complete the following information):
Additional context Please let us know if this behavior is intentional and not a bug @riknoll 😄