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

Fix bugs in email registraton + objects API prefill combination #4977

Merged
merged 3 commits into from
Dec 31, 2024

Conversation

sergei-maertens
Copy link
Member

Closes #4650

Changes

  • Fixed styling issue in registrator info template
  • Fixed registration plugin issue when objects prefill is used

Checklist

Check off the items that are completed or not relevant.

  • Impact on features

    • Checked copying a form
    • Checked import/export of a form
    • Config checks in the configuration overview admin page
    • Problem detection in the admin email digest is handled
  • Release management

    • I have labelled the PR as "needs-backport" accordingly
  • I have updated the translations assets (you do NOT need to provide translations)

    • Ran ./bin/makemessages_js.sh
    • Ran ./bin/compilemessages_js.sh
  • Dockerfile/scripts

    • Updated the Dockerfile with the necessary scripts from the ./bin folder
  • Commit hygiene

    • Commit messages refer to the relevant Github issue
    • Commit messages explain the "why" of change, not the how

Some class names and stylesheets were missing for the inline radio
choices, causing the page to look janky.
When an initial data reference is present, a registration plugin must
implement the ownership check.
…rence

Prefilling some information/variables from the Objects API in
combination with email registration is a valid use case, as requested
in issue #4650 to keep email addresses private.

The ownership check method must be implemented if a submission with
non-empty initial_data_reference is being processed - there isn't
actually anything to check since registration always sends a new
email and there is no inherent update mechanism, so there's also no
inherent object ownership.
Copy link

codecov bot commented Dec 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.66%. Comparing base (2d36304) to head (991e466).
Report is 4 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4977   +/-   ##
=======================================
  Coverage   96.66%   96.66%           
=======================================
  Files         761      761           
  Lines       25939    25940    +1     
  Branches     3392     3392           
=======================================
+ Hits        25074    25075    +1     
  Misses        601      601           
  Partials      264      264           

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

@sergei-maertens sergei-maertens merged commit 4a72d18 into master Dec 31, 2024
33 checks passed
@sergei-maertens sergei-maertens deleted the issue/4650-fix-bugs branch December 31, 2024 11:20
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.

Allow form URL-parameter to safely influence to which email address a submission is sent to
1 participant