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.

Sign up for GitHub

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

Ad missing link in BCP spec #542

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Ad missing link in BCP spec #542

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/code/BCP_Protocol/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ While the BCP protocol was created as part of the MPF project, the intention is
* Simple parameter values are prefixed with a string that indicates their data type: (`int:`, `float:`, `bool:`, `NoneType:`). For example, the integer 5 would appear in the command string as `int:5`.
* When a command includes one or more complex value types (list or dict) all parameters are encoded using JSON and the resulting encoded value is assigned to the `json:` parameter.
* Parameters are separated by an ampersand (`&`)
* Parameter names and their values are escaped using percent encoding as necessary; (details here).
* Parameter names and their values are escaped using percent encoding as necessary; ([details here](https://en.m.wikipedia.org/wiki/Percent-encoding)).
* Commands are terminated by a line feed character (`\n`). Carriage return characters (`\r`) should be tolerated but are not significant.
* A blank line (no command) is ignored
* Commands beginning with a hash character (`#`) are ignored
Expand Down