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

[#2640] Use separate field for storing long case result descriptions #1324

Merged
merged 3 commits into from
Aug 5, 2024

Conversation

pi-sigma
Copy link
Contributor

@pi-sigma pi-sigma commented Jul 29, 2024

The E-suite occasionally returns case results with descriptions that are longer than allowed by the ZGW spec (20 characters). Updating the E-suite for a single attribute is not an option. The workaround is to store longer descriptions in a dedicated attribute "naam" on ResultaatType and use it if it's non-empy, otherwise fall back on default description ("omschrijving").

Taiga: https://taiga.maykinmedia.nl/project/open-inwoner/task/2640

@pi-sigma pi-sigma force-pushed the task/2640-result-type-description branch 2 times, most recently from cdce6fe to b1a10b0 Compare July 29, 2024 10:51
@codecov-commenter
Copy link

codecov-commenter commented Jul 29, 2024

Codecov Report

Attention: Patch coverage is 96.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 95.09%. Comparing base (1edaef7) to head (292d399).

Files Patch % Lines
src/open_inwoner/cms/cases/tests/test_htmx.py 0.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1324      +/-   ##
===========================================
- Coverage    95.09%   95.09%   -0.01%     
===========================================
  Files          992      992              
  Lines        36164    36174      +10     
===========================================
+ Hits         34389    34398       +9     
- Misses        1775     1776       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pi-sigma pi-sigma force-pushed the task/2640-result-type-description branch 3 times, most recently from 60112ae to 148870e Compare August 2, 2024 12:33
@pi-sigma pi-sigma marked this pull request as ready for review August 2, 2024 13:07
Copy link
Contributor

@swrichards swrichards left a comment

Choose a reason for hiding this comment

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

Nice reorganisation of the tests too.

src/open_inwoner/openzaak/api_models.py Outdated Show resolved Hide resolved
src/open_inwoner/openzaak/tests/test_case_detail.py Outdated Show resolved Hide resolved
    - Group mocks according to API (Catalogi API, Documenten API etc.)
    - Sort API mocks according to order of dependency (e.g. Zaken API
      depends on Catalogi API but not vice versa)
@pi-sigma pi-sigma force-pushed the task/2640-result-type-description branch from 148870e to 292d399 Compare August 5, 2024 09:32
@alextreme alextreme merged commit 4f5f7d0 into develop Aug 5, 2024
18 checks passed
@alextreme alextreme deleted the task/2640-result-type-description branch August 5, 2024 12:11
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.

4 participants