You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 16, 2024. It is now read-only.
The fix involves still using the propertiesStack, but never peeking at the top if cascading is disabled.
I did some renaming in parent1-withCP; I was finding it easier to just do child1, child2, and child3, with files being named child1.json, child2.json, etc - as opposed to some being named "test.json" and some not being named that.
I added child4 to capture a scenario of - parent has C/P; child does not; grandchild does.
Copy file name to clipboardExpand all lines: src/test/resources/process-files/cascading-metadata-test/parent1-withCP/child1_2-withCP/collections.properties
Copy file name to clipboardExpand all lines: src/test/resources/process-files/cascading-metadata-test/parent1-withCP/child3_1-withCP/collections.properties
Copy file name to clipboardExpand all lines: src/test/resources/process-files/cascading-metadata-test/parent1-withCP/child3_1-withCP/permissions.properties
0 commit comments