Skip to content

Clarify current_education enrolment vs attainment (#368)#1733

Open
vahid-ahmadi wants to merge 1 commit into
mainfrom
vahid-ahmadi/issue-368-current-education-docs
Open

Clarify current_education enrolment vs attainment (#368)#1733
vahid-ahmadi wants to merge 1 commit into
mainfrom
vahid-ahmadi/issue-368-current-education-docs

Conversation

@vahid-ahmadi
Copy link
Copy Markdown
Collaborator

Summary

  • Rename current_education to current_education_enrolment #368 suggested renaming current_education to current_education_enrolment to distinguish enrolment from attainment.
  • A full rename would break every dataset row, test YAML, API consumer (policyengine-app, policyengine-household-api), and external user that currently passes current_education as input. That's too disruptive for an issue whose actual ask is "make the enrolment-vs-attainment distinction explicit."
  • Do the cheaper thing: improve the label to \"Current education enrolment\" and add a documentation string that says it's enrolment status (not attainment) and points at highest_education for the latter.
  • The variable name stays the same, so no downstream breakage. The new label/documentation is what users see in the API metadata and the docs.

Test plan

  • Microsimulation() builds and system.variables[\"current_education\"].label returns the new label.

🤖 Generated with Claude Code

#368 suggested renaming current_education -> current_education_enrolment
to distinguish enrolment from attainment.

A full rename would break every dataset row, test YAML, API consumer
(policyengine-app, household-api), and external user that passes
current_education as input. Too disruptive for an issue whose actual
ask is "make the enrolment-vs-attainment distinction explicit".

Do the cheaper thing: improve the label to "Current education
enrolment" and add a docstring that says it's enrolment status, not
attainment, and points at highest_education for the latter. The
variable name stays the same so no downstream breakage; the label is
what users see in the API metadata and the docs.
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.

1 participant