Remove `budgetary_impact` from the `set_user_policy` endpoint's unique record testing

PolicyEngine / policyengine-api

PolicyEngine's REST API for computing policy impacts.

GNU Affero General Public License v3.0

7 stars 20 forks source link

Remove `budgetary_impact` from the `set_user_policy` endpoint's unique record testing #1460

Closed anth-volk closed 2 months ago

anth-volk commented 2 months ago

Fixes #1459. This ensures that budgetary_impact isn't treated as a unique key within a record, preventing duplicate record creation when a user accesses their profile.

anth-volk commented 2 months ago

I'm starting to think there's a more fundamental issue in #1459. I'm converting this to draft so that I can dig into this more.

anth-volk commented 2 months ago

Upon local testing, this PR does appear to solve the issue; converting back to "ready for review"