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

Document how parameters in sections are referenced #11026

Merged
merged 4 commits into from
Jan 12, 2021

Conversation

bernt-matthias
Copy link
Contributor

@bernt-matthias bernt-matthias commented Jan 1, 2021

Quite confusing for tool developers ...

Maybe parts of the text could be duplicated / moved to other parts of the docs.

Is it a bug that cross referring inputs is only possible on the same or parent levels? From inspecting the code it also appeared to me that the reference needs to be before the referring parameter (in the xml file). The reason for both is in this function

def parse_input_elem(self, page_source, enctypes, context=None):

Copy link
Member

@bgruening bgruening left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @bernt-matthias for improving our tool documentation constantly, this is really appreciated!

lib/galaxy/tool_util/xsd/galaxy.xsd Outdated Show resolved Hide resolved

Until profile 21.01 `parameter_name` was sufficient (https://github.com/galaxyproject/galaxy/pull/9493/files).

Note that references to other parameters in the `<inputs>` section are only possible if the reference is in the same section or its parents, therefor only `parameter_name` is used.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide an example here?

In theory we could have a parameter foo in the top-level inputs and a parameter foo in a section. Do we?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide an example here?

Yes.

In theory we could have a parameter foo in the top-level inputs and a parameter foo in a section. Do we?

Yes, but this is discouraged ... nevertheless it might occur in automatic tool building (e.g. in OpenMS I had the case, but luckily no cross reference was needed). Wondering if we should file an issue for this?

@bernt-matthias
Copy link
Contributor Author

Since this is the same for repeats and conditionals .. is there a way to have this docs also there? Also it would be good to link this to the docs of format_source, metadata_source, and data_ref, or?

Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
@mvdbeek mvdbeek changed the title document how parameters in sections are referenced Document how parameters in sections are referenced Jan 12, 2021
@mvdbeek mvdbeek merged commit a4bed8e into galaxyproject:dev Jan 12, 2021
bernt-matthias added a commit to bernt-matthias/galaxy that referenced this pull request Sep 17, 2021
galaxyproject#11026 extended the
description on how parameters in sections are referenced.

this already included syntax that is not merged yet:
galaxyproject#9493

this PR reverts this, see galaxyproject#9493 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants