Conversation
Contributor
Author
|
Superseded by PolicyEngine/policyengine-sim-api#705. The replacement identifies the authority roster from actual la_code_oa values and does not route lookup data by dataset name or release identity, so no PolicyEngine.py change is required. |
Contributor
Author
|
Update: the replacement simulation API work is now PolicyEngine/policyengine-sim-api#706. GitHub closed #705 when its branch was renamed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #541
Adds typed bundle metadata for the LAD22 and LAD23 lookup assets. Explicitly listed legacy UK dataset identities resolve to LAD22; every other identity defaults to LAD23. Managed lookup files are verified against pinned SHA-256 hashes before use, while an explicit caller-owned path remains an intentional override.
The local-authority output accepts the managed dataset identity so service callers can select metadata that matches the codes emitted by the dataset.
Test plan: