Skip to content
This repository has been archived by the owner on Apr 28, 2022. It is now read-only.

[FIX] - Readonly / Required #88

Conversation

richard-willdooit
Copy link
Contributor

@richard-willdooit richard-willdooit commented Apr 30, 2017

Dynamic readonly / required on pop-ups need to assume that
if they are based on different domain records then they are "or"
instead of "and".

@richard-willdooit richard-willdooit changed the title [ENH] - Readonly / Required [FIX] - Readonly / Required Apr 30, 2017
@PCatinean
Copy link
Contributor

@richard-willdooit the tests have stopped for some reason on all PR's.

I'm not sure exactly what the cause is but I need to get it fixed before merging onto the stable branches.

Dynamic readonly / required on pop-ups need to assume that
if they are based on different domain records then they are "or"
insted of "and".
@codecov-io
Copy link

codecov-io commented May 8, 2017

Codecov Report

Merging #88 into 10.0 will decrease coverage by 0.48%.
The diff coverage is 0%.

Impacted file tree graph

@@            Coverage Diff             @@
##             10.0      #88      +/-   ##
==========================================
- Coverage   61.11%   60.62%   -0.49%     
==========================================
  Files          14       14              
  Lines        1368     1379      +11     
==========================================
  Hits          836      836              
- Misses        532      543      +11
Impacted Files Coverage Δ
...configurator_wizard/wizard/product_configurator.py 32.31% <0%> (-0.94%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 89750da...633d391. Read the comment docs.

@richard-willdooit
Copy link
Contributor Author

@PCatinean If you think this is more important than the other fix #97 then I will look at the tests, but I would like to get #97 merged before I write more tests in areas which will have conflicts.

@richard-willdooit
Copy link
Contributor Author

Again, #104 deals with this more logically

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

Successfully merging this pull request may close these issues.

3 participants