Repository navigation
Conversation
Add adcom_list_names() so the AdCOM list registry can be enumerated, and an export_site_reference example that writes field-reference.json and adcom-lists.json from the static catalogs and version profiles. The site uses them for per-field and per-list reference pages. No validator behavior changes. The exporter supplements four parent links the catalogs do not resolve (Device.sua, UserAgent.browsers, and the 2.2 regs and deals objects) when building paths.
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.
Summary
adcom_list_names(), a read-only accessor for the AdCOM list registry. Paired with the existingadcom_list_values(), it lets callers export the full registry.export_site_referenceexample. It writesfield-reference.json(every OpenRTB 2.x object and field across the 16 tracked versions with catalogs: types, required and deprecated markers, AdCOM list references, value sets, spec sections, reachable paths, and the versioned rules that name each path) andadcom-lists.json.No validator behavior changes.
Catalog gap found while exporting
Four parent fields have no resolved
child_objectin the catalogs:Device.sua(UserAgent),UserAgent.browsers(BrandVersion), and the 2.2BidRequest.regsandPmp.deals. The exporter supplements these links for path building only. Worth checking whether the validator descends intodevice.suaandsua.browsersfor type checks; that is left for a separate change.Test plan
cargo test -p rtblint-core: 278 passed.cargo clippy -p rtblint-core --examples: clean.cargo run -p rtblint-core --example export_site_reference -- <dir>: 40 objects, 16 versions, 43 AdCOM lists.🤖 Generated with Claude Code