renderData + Computed Data

[Snugug]

Describe the bug
When combining renderData and Computed Data, the end result is the un-rendered string version of renderData (so something like {{foo.bar}}). It looks like you're looking to deprecate renderData in favor of Computed Data, but my current scenario requires both: I'm using pagination to generate localized versions landing pages, and the titles for those landing pages aren't held in a title attribute, but rather a nested attribute that I was using renderData to surface, then normalizing that (and other generic places where title may be stored) and creating a data cascade to surface it. Without renderData available, I need to hunt and peck for individual page URLs in Computed Data to get the right title, which is harder to maintain than keeping it in renderData in the template.

To Reproduce
Steps to reproduce the behavior:

1. Create a data-driven paginated output
2. Include a renderData property from an attribute in the data
3. Use Computed Data to retrieve the value of the above property
4. Note it not being rendered

Expected behavior
Expect that renderData is resolved as part of computed data

Environment:

• Eleventy Version 0.11.0