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

Parametrize OpenKlant2 params voor Mijn Vragen functionality #1431

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

swrichards
Copy link
Contributor

This is mostly to serve as a loud and prominent reminder to move these parameters to a configuration model when we start hooking up this service to the core views.

@codecov-commenter
Copy link

codecov-commenter commented Oct 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.58%. Comparing base (7f883b0) to head (2e8d6aa).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1431   +/-   ##
========================================
  Coverage    94.58%   94.58%           
========================================
  Files         1069     1069           
  Lines        39623    39623           
========================================
  Hits         37478    37478           
  Misses        2145     2145           

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

@swrichards swrichards force-pushed the tasks/2789-parametrize-ok2-params branch from ef6abe4 to c5f4db7 Compare October 9, 2024 08:16
The question/answer flow in OpenKlant2 requires a fair number of
parameters. For now, these are hard-coded as constants, but when
we hook everything up they should be replaced with configurable
fields. This commit makes this a bit clearer in the form of a
TODO and signposted variables.
@swrichards swrichards force-pushed the tasks/2789-parametrize-ok2-params branch from c5f4db7 to 2e8d6aa Compare October 9, 2024 09:03
@swrichards swrichards marked this pull request as ready for review October 9, 2024 09:03
@alextreme
Copy link
Member

PR is of course fine, but I'm going to leave this PR open until the TODO is resolved

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.

3 participants