Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
A more complete solution would be for Asciidoctor core (the ruby code) to support a context which it would use to resolve interpolation. We could then plugin all sorts of things: pojos, hashes, json, etc. — Sent from Mailbox for iPhone On Sat, May 11, 2013 at 11:30 AM, asotobu [via Asciidoctor :: Discussion] <[hidden email]> wrote:
... [show rest of quote] |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
yes this would be even better, when I opened the discussion it was only to affect the Java part, but of course, it is better if we can plug in the interpolation code.
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Thoughts Dan? On Sun, May 12, 2013 at 4:13 AM, asotobu [via Asciidoctor :: Discussion] <[hidden email]> wrote: yes this would be even better, when I opened the discussion it was only to affect the Java part, but of course, it is better if we can plug in the interpolation code. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
|
I agree this would be a great feature. At the very least, we should introduce an extension point to handle attribute resolution (reminiscent of an EL resolver in Java EE, though far less complicated). I do think it's reasonable to support a basic object graph natively as well. Wrapping an OpenStruct around just about any data model allows you do reference the members using the proposed dot notation...and that keeps the document simple. My reply on this thread was triggered by a discussion I had at OSCON. The person I was talking to needed to be able to populate the document with structured data and it relied on being able to traverse the graph in the attribute references (e.g., {borrower.firstname}). This use case is also present in the Awestruct integration (e.g., {site.name}). Thus, I'm escalating it to a must have, in some form.
I'll create an issue for this feature so we can discuss how it should work, how it should be implemented, etc. -Dan On Mon, May 13, 2013 at 11:08 AM, lightguard.jp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
... [show rest of quote] Dan Allen | http://google.com/profiles/dan.j.allen
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
|
In reply to this post by LightGuardjp
On Tue, Jul 30, 2013 at 6:11 PM, Dan Allen <[hidden email]> wrote:
... [show rest of quote] Dan Allen | http://google.com/profiles/dan.j.allen |
Free forum by Nabble | Edit this page |