-
Notifications
You must be signed in to change notification settings - Fork 8
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
Move the visible check to alert banner manager #355
Conversation
bce895b
to
f621db9
Compare
@millnut do you know what's happening here? |
Composer is failing to install the testing branch because the This bit of code is showing itself to be a bit flaky. We either need to make the API call more reliable or create a variable that allows us to override the default value. The latter might be easier. |
@stephen-cox I wonder whether we can use a github action step to get the latest tagged release? Would that work? |
The API call in the workflow is supposed to do this for the major release, but in this case, because the target branch contains a minor release number the command is failing. This looks to be due to the bash string operations not being able to handle this case. I think I have a fix for this and will create a PR in the shared workflows for it. |
There's a fix for this here: localgovdrupal/localgov_shared_workflows#4 If we're happy with this then we can merge and then rerun the tests (after resetting the cache variable) and tests should run. |
f621db9
to
45946fe
Compare
834ce8f
to
ef239c5
Compare
This is update to include a test for the scenario we encounterd in #327 where the cache contexts of the block meant the banner did not show. Interestingly I found out that checking for visibility did not seem to matter, but that might be as we are not negating yet. However it is important that the containing block does have cache contexts and if this api is extended we might want to offer an api to get cache contexts. |
ef239c5
to
0209c01
Compare
Anything that @localgovdrupal/maintainers want to comment on, or can I merge this as this should be enough to get a 1.8.0 release next merge Tuesday. |
See #327. Extends visibility test by providing actual pages for the banner to display on. This also provides an extra banner to test the correct banner is visible per page.
0209c01
to
69e4167
Compare
Going ahead and merging this. |
Fix #354