Parser idea

[Gelbpunkt]

This is a first take at a parser for a human-readable protocol. Targets #15

It's WIP and I'll start separating it onto multiple files when the syntax itself gets accepted.

There's 5 actions: CONNECT, PING, INFO, REQUEST, RESPOND
All can be called simply with ACTION;, except REQUEST and RESPOND.
Those require arguments, e.g. REQUEST 'json goes here';.
Optionally, they take a FROM/TO argument that is either ALL or an integer of e.g. the receiver.
CONN, REQ and RESP are aliases.

Examples:

CONNECT;
REQUEST 'whatever';  # Equals REQUEST 'whatever' FROM ALL;
REQUEST "whatever" FROM 2;  # Double quotes work, too
RESP "hello" TO 3;  # Respond to a specific sender

I made a simple interactive example. You can run it like this:

python3 yarpc/parser.py

Then type your queries and it'll output the actual query string or syntax errors.

Note: Syntax is subject to change, I might go for REQUEST 'handler_func' WITH 'parameter1', 'parameter2', 3 FROM ALL;. But that would remove the JSON-ish syntax

[codecov]

Codecov Report

Merging #30 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #30   +/-   ##
======================================
  Coverage    53.9%   53.9%           
======================================
  Files          14      14           
  Lines         371     371           
======================================
  Hits          200     200           
  Misses        171     171

Impacted Files	Coverage Δ
jarpc/types.py
jarpc/typing.py	100% <0%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6de165e...310352a. Read the comment docs.

[Gelbpunkt]

That's the next step when parser is done

[Fogapod]

Not sure how this should work under the hood. Are you only going to work on parser or you can suggest changes to library internals as well?