Juraj Kirchheim

[talk] Making the most of Haxe

2

Sorry for the delay. Will make a talk page soon ;)

Allow <expr> <identifier> <expr> call Syntax

8

IIRC, Scala allows you to write ` ` to denote `.()`. With support for this, #17 would be easy to solve. Just have `using RaxeWords` with this: ``` extern class...

Dependency on `hxnodejs` is causing issues with socket.io in browser

9

This is a follow up on #141, however the problems we encounter are more far-reaching. Among other things hxnodejs: - sets `-D nodejs` which is why [`haxe.Http` will attempt using...

Header params case sensitive.

1

I just had `@:params(token = header['X-Gitlab-Token'])` yield a 422, due to the casing.

Previously, it was possible to capture the remainder of a path via `@:get('/x/y/z/*rest')`.

Facade for tink_web

5

To facilitate usage of tink_web (especially for newcomers), I propose putting a facade in `tink.Web`: ```haxe package tink; class Web { static macro function serve(root:Expr, ?options:Expr); static macro function connect(target:Expr,...

Mostly, this is to properly support returning plain data on POST against the API while having Post/Redirect/Get on the same route when coming from a browser.

Given the route + `@:html` information, it should be possible to construct a client side renderer. - [ ] Intercept navigation and form submission - [ ] Perform interrupted request...

- [ ] allow adding `@:html` on classes - [ ] find a solution to set title from within concrete route - [ ] support breaking out of nesting

Consider marking @:get as @:pure by default.

4

Following the reasoning in https://github.com/haxetink/tink_http/issues/105 it should actually be ok to mark safe methods as `@:pure` on remoting proxies. This will allow the compiler to optimize away quite a bit...