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.

Sign up for GitHub

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

Jump to bottom

transform dispatcher #1401

Closed
markus2330 opened this issue Mar 5, 2017 · 1 comment
Closed

transform dispatcher #1401

markus2330 opened this issue Mar 5, 2017 · 1 comment
Labels
low priority question

Comments

@markus2330
Copy link
Contributor

Thus renaming tasks (such as #1400), splitting tasks ( #1395) always contain a very similar logic (remember what we transformed, so that we can transform back afterwards), we might profit from a framework that takes away the burden of back-transformation logic.

The question is how general can it be:

  • just renaming would be trivial (we could add this functionality to rename plugin then)
  • splitting (1:N)
  • splitting and merging (N:M)
@markus2330
Copy link
Contributor Author

Enough frameworks for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
low priority question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@markus2330