Moritz Schmale

@brooksmtownsend this is off-topic, but I can recommend using `asdf` for managing developer dependencies where you can pin on the exact version you need, per project even.

Yeah, that happens when you use the URI class wrongly. This is how I'm decoding the string: ``` java String json = new String(Base64.getDecoder().decode(uri.getRawSchemeSpecificPart().substring(2))); ```

My point is that you're probably extracting the base64 part of the URI wrong. Base64 is not the problem and evidently works. Check if your code puts the correct base64...

Ah that sucks then. Should make the URL smaller and just pass some id which then is used on the API.

@Zequez you should somehow make your URL shorter because Windows apparently doesn't like long URLs.

Thanks, that worked :)

probably should change it to `any`, since it could also be that a value from the scope is returned, which can really be anything.

that was quick. before I properly review it, at first glance it looks good, but I have no clue if a deep variable access in polish notation is the same...

I think it could be implemented as another parse function, like parse_polish or so. The resulting AST would be the same (as it's elixir AST anyway).

I'll gladly accept a PR that adds a second function to parse a different syntax into the same internal representation (the AST). If you need any pointers, feel free to...