[Feature request] Run computed properties in dependency order

[kevinpschaaf]

Description

Currently computed properties with invalidated dependencies are re-computed based on a combination of order they exist in the properties block and the order that dependencies are set, and will continue re-computing if subsequent dependent properties change. This can result in computed properties running more than once in a turn, which is both inefficient if the computed property has expensive computation/side-effects, and may violate user expectation.

Live Demo

https://jsbin.com/lofapu/1/edit?html,console

Expected Results

Note that computeZ is run twice for the same change to x

Actual Results

Ideally computeZ would only be run once

Browsers Affected

All

Versions

• Polymer: v2.x

[kevinpschaaf]

Proof-of-concept mixin that recurses to run computed dependencies of a computed proeprty first: https://jsbin.com/dewewah/edit?html,console

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rubenlg]

Stale? Isn't it fixed already?