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

Release Y24-052 [BUG] Dropdown list dependencies #4088

Merged
merged 28 commits into from
Apr 22, 2024
Merged

Release Y24-052 [BUG] Dropdown list dependencies #4088

merged 28 commits into from
Apr 22, 2024

Conversation

KatyTaylor
Copy link
Contributor

Closes #

Changes proposed in this pull request

  • Fix for Admin Study Edit page
    • Modification of legacy_javascript_tag so that the javascript runs even if it is rendered after page load
  • (flagged off) Server-side validation for relationship between Study fields - data release strategy and data release timing
  • New Flipper feature flag for the above
  • Addition of two filters to the PolyMetadatum API resource (to support Y24-028 Targeted Nanoseq fix)

Instructions for Reviewers

[All PRs] - Confirm PR template filled
[Feature Branches] - Review code
[Production Merges to main]
    - Check story numbers included
    - Check for debug code
    - Check version

depfu bot and others added 28 commits April 3, 2024 18:30
…ta release 'strategy' and 'timing' fields

- add 'validates' methods on study metadata
- add constant for 'immediate' timing to study, following existing pattern
- add tests for the new validation
- amend existing tests that were creating invalid data
- They enforce the relationship between data release strategy and timing that is required by the Study creation and edit UI
…date

Y24-028 Targeted NanoSeq - added filters on polymetadata resource
[ruby] Update nokogiri 1.16.2 → 1.16.4 (patch)
🚨 [security] [js] Update vite 5.1.5 → 5.1.7 (patch)
- the JS inside the legacy_javascript_tag in _related_fields.html.erb wasn't running at all, when rendered on the admin studies edit page
- this was because the page was already loaded, so the event listener never heard the 'DOMContentLoaded' event
- the page was already loaded because the edit page is rendered inside the index page, only after a value is selected from the dropdown list of studies
- add an 'if' statement in the legacy javascript tag to check if the page is still loading before listening for the event
- if the page is not still loading, just render the contents without waiting for the event
[ruby] Update json 2.7.1 → 2.7.2 (patch)
- there is a lot of existing data that would trigger this validation currently
- flag this off until the data is fixed
- improve tests
- add tests for when the feature flag is on and when it is off
…encies

Y24-052 [BUG] Dropdown list dependencies
Copy link
Contributor

@sdjmchattie sdjmchattie left a comment

Choose a reason for hiding this comment

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

I can't say I understand the logic being implemented, but the code looks good and it looks thoroughly tested.

@KatyTaylor KatyTaylor merged commit 815d149 into master Apr 22, 2024
24 checks passed
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

Successfully merging this pull request may close these issues.

5 participants