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

Missing '0' in 'serial write buffer serial read buffer 0' help documentation #5665

Closed
v-katherine opened this issue May 10, 2024 · 5 comments · Fixed by microsoft/pxt#10061
Closed
Assignees
Labels

Comments

@v-katherine
Copy link

Describe the bug
Missing '0' in 'serial write buffer serial read buffer 0' help documentation

Steps to reproduce the behavior
1.Navigate to https://makecode.microbit.org/beta
2.Create or open a project.
3.Toolbox->Serial more, open the help documentation of block 'serial write buffer serial read buffer 0'.
4.Compare the block in Toolbox and help documentation.

Actual behavior:
Missing '0' in 'serial write buffer serial read buffer 0' help documentation

Expected behavior:
Should update the block in doc that same with in the Toolbox.

Screenshot:
block0

Additional context:
1.OS: Windows11, iMac Ventura 13.6.6
2.makecode.microbit,org version: 7.0.9
3.Microsoft MakeCode version: 10.0.21

@ganicke
Copy link
Collaborator

ganicke commented Jul 29, 2024

@abchatra, @riknoll - somehow number parm is dropped after decompile to blockly render:

```sig
serial.writeBuffer(serial.readBuffer(0))
```

image

RE: #5663

@v-katherine
Copy link
Author

Verified this issue on the lasted makecode.microbit version: 7.0.15, it still reproduces, so I reopen it now.

@v-katherine v-katherine reopened this Aug 2, 2024
@riknoll
Copy link
Member

riknoll commented Aug 5, 2024

@v-katherine this is fixed, but you won't be able to see it because our docs pages are always tied to the live released version. The fix will show up once beta is released to live

@v-katherine
Copy link
Author

v-katherine commented Aug 6, 2024

@riknoll Okay, Thanks for your information, I will track this issue and update the result once the fix show up in beta version.

@fionama100
Copy link

I have verified this bug in the latest build: 7.0.16 and it has been fixed. Close it now.
Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants