-
Notifications
You must be signed in to change notification settings - Fork 10
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
Transform4: TAP Contents #31
Comments
|
I'm not saying that, I'm asking it as a question. I should have made that clear. These are all possible situations that one may encounter, so we should decide and document our decisions. As for the Boolean, I agree that they should be configurable, but as we do not yet have a model for a configuration file we should discuss what values we want to accept as default. I hope others will weigh in. |
Are you saying that a bad value node type should be passed through to the
output?
I'm not saying that, I'm asking it as a question.
But it's a good question. One general approach would be to let everything
pass through with a warning that says "by the way, we don't recognize
this".
Another, opposite-extreme, approach would be to delete everything that is
not recognized so that users will see the gaps more clearly.
|
My gut feeling is that warning but passing through is the way to go. |
+1 to that
…On Fri, Jun 11, 2021, 19:25 Karen Coyle ***@***.***> wrote:
My gut feeling is that warning but passing through is the way to go.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#31 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIOBJUF43ISFKKHVFSJRILTSJBIBANCNFSM45U6JP2A>
.
|
See dctap-python documentation for resolution. |
This should be just the minimum for this version. It could also be skipped if we run out of time, so ideally outputs should be completed before this is done.
The text was updated successfully, but these errors were encountered: