-
Notifications
You must be signed in to change notification settings - Fork 6
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
[#2098] Show case-related questions in case detail view #1059
Conversation
bceaad1
to
931d85b
Compare
75f91e7
to
e780963
Compare
@stevenbal @jiromaykin I thought it makes sense to paginate the questions for particular cases, though it is not entirely straightforward (we need to paginate inside a detail view + the query param for the page is not easily accessible because of the inner/outer view split for cases). Let me know if this functionality is not needed, then I'll get rid of it. I just saw that this was requested as part of a follow-up (Taiga #2148) |
So, I think we agree the pagination is not needed for the detailview - the detailview needs a collapse/readmore button. |
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.
I need more 'Vragen' data in order to properly review this.
96c8b93
to
1fb0ac6
Compare
4b14943
to
e59fb16
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1059 +/- ##
=========================================
Coverage 95.00% 95.01%
=========================================
Files 896 909 +13
Lines 31449 31917 +468
=========================================
+ Hits 29879 30325 +446
- Misses 1570 1592 +22 ☔ View full report in Codecov by Sentry. |
5835a93
to
769b099
Compare
701449a
to
c1c6ab9
Compare
c967536
to
bfb2dfc
Compare
bfb2dfc
to
51e14f2
Compare
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.
I am not sure how to fix the tangled javascript, but if we change the 'dropdown' class into an 'expand' class than this may work as an intermediate solution.
Also some small requests to change the Card SCSS and some html classes for the primary buttons.
{# redirect to fetch klantcontactmoment from contactmoment #} | ||
<a href="{% url 'cases:kcm_redirect' contactmoment.uuid %}" class="card card--compact card--stretch card--toggle-hide contactmomenten__link"> | ||
<div class="card__body"> | ||
{% render_list %} |
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.
There might not be a need to use a UL or list-items inside this card.
But I am not sure if this is the definite design:
https://www.figma.com/file/iKGhWhstaLIlFSaND2q7cE/OIP---Designs-(new)?type=design&node-id=1839%3A12002&mode=design&t=BLYIn4BeQOFtBCyU-1
51e14f2
to
c4159e8
Compare
c4159e8
to
1dbbf08
Compare
1dbbf08
to
1025af6
Compare
1025af6
to
fcddaf8
Compare
created=dateutil.parser.parse( | ||
self.zaak_informatie_object_old["registratiedatum"] |
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.
Note for other reviewers: we discussed this and dateutil.parser.parse
is acceptable here because the zgw_consumers factory()
also uses that and it produces different timezones then datetime.fromisoformat
so the equality check failed.
There might be a way to convert it but let's declare that out of scope for this PR because it is a hassle.
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.
👍 Let's go! 🚀
fcddaf8
to
c8f3f74
Compare
Taiga: #2098
Related: PR #1045