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

Find better way to specify input #39

Closed
marcverhagen opened this issue Dec 21, 2016 · 1 comment
Closed

Find better way to specify input #39

marcverhagen opened this issue Dec 21, 2016 · 1 comment

Comments

@marcverhagen
Copy link
Member

We are quite unhappy with source=X as an option. May want to introduce format=X with X in [xml, text, ttk] and another option, but naming is tricky (genre?, domain? input-type?) and there are interactions between format/domain and what processing has already been done.

Related to #14 and #18.

@marcverhagen marcverhagen mentioned this issue Dec 1, 2020
16 tasks
@marcverhagen
Copy link
Member Author

marcverhagen commented Dec 1, 2020

With the LIF format added (see issue #88) we have seemingly also added an inconsistency in that TTK always creates TTK except when the input is LIF as indicated by --source=lif.

It is probably better to use two parameters:

  1. Use --input-format to avoid or overrule guessing of what the input format is. This can also be used to deal with the issue we have with the --pipe parameter which makes the guess currently impossible (issue Guessing the source breaks when --pipe is used #71).

  2. Use --output-format to overrule the ttk default.

This doesn't solve the problem of potentially wanting to write domain specific code, but we can deal with that if needed by adding a --domain parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant