-
Notifications
You must be signed in to change notification settings - Fork 369
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
feat: IAB statements #5940
feat: IAB statements #5940
Conversation
* feat: infrastructure for statements doctype * chore: basic test framework * feat: basic statement document view * feat: show replaced statements * chore: black * fix: state help for statements * fix: cleanout non-relevant email expansions * feat: import iab statements, provide group statements tab * fix: guard against running import twice * feat: build redirect csv for iab statements * fix: set document state on import * feat: show published date on main doc view * feat: handle pdf statements * feat: create new and update statements * chore: copyright block updates * chore: remove flakes * chore: black * feat: add edit/new buttons for the secretariat * fix: address PR #5895 review comments
Codecov Report
@@ Coverage Diff @@
## main #5940 +/- ##
==========================================
- Coverage 88.67% 88.62% -0.05%
==========================================
Files 288 290 +2
Lines 40001 40178 +177
==========================================
+ Hits 35471 35609 +138
- Misses 4530 4569 +39
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One fix needed, plus a question
@@ -40,7 +40,7 @@ | |||
# 'ietf.context_processors.sql_debug', | |||
# ] | |||
|
|||
DOCUMENT_PATH_PATTERN = '/assets/ietf-ftp/{doc.type_id}/' | |||
DOCUMENT_PATH_PATTERN = '/assets/ietfdata/doc/{doc.type_id}/' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move the assets around on the dev container before merging this, or deal with it later? (Earlier you said there'd be other fallout -- just confirming whether this is intentional or was forgotten)
No description provided.