Access closure property names in the content block at runtime

[geb-bot]

Originally created by William Lucas.

Per conversation back in Oct:

http://stackoverflow.com/questions/26681458/access-closure-property-names-in-the-content-block-at-runtime

[geb-bot]

Originally posted by William Lucas.

Hi Erdi, do you have any idea when this might be completed? It would be useful for test maintenance!
Thanks.

-Will

[geb-bot]

Originally posted by Marcin Erdmann.

Will, tbh, this is not at the top of the backlog at the moment. I need to first migrate all issues from here to github because Codehaus is shutting down soon. After that, I need to finish migration of the Book of Geb to asciidoctor while making all examples executable at the same time. I banned myself from touching any code before finishing, otherwise I would be just feeding my procrastination habit. There is one exception form the rule though - pull requests are always the highest priority so if you really care about this feature then please kick off a thread on the dev list and I will be happy to give you pointers.

[geb-bot]

Originally posted by William Lucas.

Hi Erdi, Just seeing this now. Did you migrate the 'Book of Geb' to asciidoctor?
Are all the the issues in github?
Not sure what you meant by "kick off a thread on the dev list"? Does this mean my request will die on the vine (i.e. not be migrated to github?) Thanks, Erdi!

[geb-bot]

Originally posted by Marcin Erdmann.

Migrating the "Book of Geb" to asciidoctor is now on on the back burner because I'm working on migrating issues from here to GitHub issues. It's almost ready, I've just hit some issues with GitHub API but I've learned how to resolve them and need a tiny bit more time to finish it off. Nothing will die on the vine, all issues from this tracker will be migrated to the new tracker at GitHub.

By kicking of a thread at the dev list I meant asking questions at https://groups.google.com/d/forum/geb-dev about implementation details if you were willing to work on a pull request with this feature. This feature is not a priority for me at the moment so you should expect several months for it to be implemented unless you speed this up by providing a pull request.