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

allow to push attribute's diff from above #85

Open
sopos opened this issue Nov 11, 2020 · 2 comments
Open

allow to push attribute's diff from above #85

sopos opened this issue Nov 11, 2020 · 2 comments

Comments

@sopos
Copy link

sopos commented Nov 11, 2020

Normally one can do

require:
  - a
/X:
  require+:
    - b

In the tmt the test case normally defined require: so it replaces eventual parents require:.

Now, the use case is to be able to force some requirement from the parent to the childs.

+require:
  - a
/X:
  require:
    - b

This +require: would ackt the same as require+: but applied in opposite order. So every child node would append it. It might be reset as usual +require: '' or added, deducted by +require+:, +require-: respectively.
The same forced deduction might work with -require:.

What I want to achieve:
instead of updating all the test with requirement for a library referenced with url/name I would propagate it this way so I can manage it centrally.

@lukaszachy
Copy link
Collaborator

Just an obvious note: By solely using merging in children nodes (everywhere require+) you can achieve desired effect right now.
However with this new merging prefix one will be unable to override parent's attribute.

@sopos
Copy link
Author

sopos commented Jan 4, 2021

After some thinking I must say that if this is implemented it should be done on tmt side.
Simply +require would be treated as any other attribute (redefining, adding, deducting works as normally).
Just tmt would merge +require and require into a final require.
The workaround with using require+ everywhere is also possible it is just not that convenient.

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

2 participants