Allow partial expansion of templates about mustermann HOT 6 CLOSED

I'd love this feature, btw. It would require a more complex (thus potentially slower) data structure, since you'd actually have to generate a new Pattern object from the Expander.

I think building a separate PartialExpander along side Expander would allow people to opt into the added computational and/or memory cost (I think it would be very easy to sacrifice memory for performance).

from mustermann.

Care to pair on this? Friday maybe, or next week?

from mustermann.

I'd like to. I'm pretty busy right now until I get back from Israel November 8, unfortunately.

from mustermann.

ok, no rush. I'll ping you in a couple weeks then :)

from mustermann.

Which features do you expect?

Things that could be possible but will influence the API, internals and performance:

1. Generating URI template strings.
2. Generating objects that support further expanding.
3. Generating full pattern objects (ie, that support matching).
4. Generating string representations in the actual pattern type (ie, expand /:a/:b to /foo/:b).

Of these, 2 would probably be easiest to implement (since it's just a proxy) and can be combined with any of the other, 1 is likely what you want. 3 should be feasible, 4 might be too much work for a feature people will rarely if ever use.

The most complex pattern type to implement this for would be URI templates itself (at least if level 4 expansion is the goal), it would share quite some logic with the full expansion, which also has some broken edge cases right now (see #4 and #5).

I could also imagine a partial expander to use the same logic as the full expander, but this might come at high memory cost (though I'm not 100% sure that's true, since for patterns with a reasonable number of variables, keeping the AST around would probably use more memory - the expander currently only needs the AST when generating expansion rules).

from mustermann.

Links in Yaks have the option to only expand none, all, or some of the placeholders

link :self, '/api/posts/{id}'
link "/rel/comment", '/api/posts/{id}/comments/{comment_id}', expand: [:id]
link "/rel/search", '/api/search{?q}', expand: false

Which would render as (using HAL as an example)

"_links": {
  "self": {"href": "/api/posts/7"},
  "/rel/comment": {"href": "/api/posts/7/comments/{comment_id}", "template": true},
  "/rel/search": {"href": "/api/serach{?q}", "template": true},
}

So I guess that's 4?

from mustermann.