This repository has been archived by the owner on Feb 28, 2022. It is now read-only.
Expose VDOM Transformer in action #325
Assignees
Labels
Comments
trieloff
added a commit
that referenced
this issue
Sep 4, 2019
This enables the easy, additive setting of handler functions in pre.js without having to reproduce the entire VDOM configuration Fixes #325
trieloff
added a commit
that referenced
this issue
Sep 5, 2019
adobe-bot
pushed a commit
that referenced
this issue
Sep 13, 2019
# [5.4.0](v5.3.1...v5.4.0) (2019-09-13) ### Features * **pipeline:** expose vdom transformer in action ([2df18b9](2df18b9)), closes [#325](#325)
|
🎉 This issue has been resolved in version 5.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Managing the VDOM Transformer yourself creates potential for issues like #132 – instead I'd like to expose it as part of the action in
action.vdom, so that new matchers, etc. can get registered easily, enabling customization of the generated HTML as requested in #320The text was updated successfully, but these errors were encountered: