Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposition to improve the transformer workflow #24

Merged
merged 4 commits into from
Dec 20, 2012
Merged

Proposition to improve the transformer workflow #24

merged 4 commits into from
Dec 20, 2012

Conversation

blanchonvincent
Copy link
Contributor

Wrap the source with the stream metadatas. Because, someone transformer
need source, someone do not need source. With a global wrapper (the
StreamMetaData), each transform is based on only one object.

@blanchonvincent
Copy link
Contributor Author

@lisachenko it's just a proposition, give me your feedback.

Wrap the source with the stream metadatas. Because, someone transformer
need source, someone do not need source. With a global wrapper (the
StreamMetaData), each transform is based on only one object.
@lisachenko
Copy link
Member

@blanchonvincent good idea! 👍 This gives more stable interface for transformers.

However, for future I want to use PHP-parser library and Abstract Syntax Tree as source instead of string and StreamMetaData. Transformers will be rewritten as node visitors, this will give more control on source code.

@lisachenko lisachenko merged commit 7d3f6a4 into goaop:master Dec 20, 2012
genkiroid pushed a commit to genkiroid/framework that referenced this pull request Jun 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants