diff options
| author | Tobin Ehlis <tobine@google.com> | 2017-05-24 09:31:13 -0600 |
|---|---|---|
| committer | Tobin Ehlis <tobine@google.com> | 2017-05-24 11:21:40 -0600 |
| commit | 23b468e1bf7369de108c28bf094acae98add5130 (patch) | |
| tree | 31e46770c0cb5d55cfea74fc9f519535c0a16dc0 /scripts/parameter_validation_generator.py | |
| parent | 8ce219c4526dafda036ac33a3877f429d107f837 (diff) | |
| download | usermoji-23b468e1bf7369de108c28bf094acae98add5130.tar.xz | |
layers:Migrate to new validation error IDs
Migrate valid usage IDs to new numbers based on the string IDs that are
integrated into the spec build process.
The formula for mapping the string ID to the new VALIDATION_ERROR enum
value is in vuid_mapping.py script.
The mapping between the old IDs and the new IDs is in the file
"old_vuid_to_new_mapping.txt."
The vk_validation_error_database.txt file has the new IDs as well as
the string-based ID for each element and a column indicating if the
valid usage is in the core spec or if it requires extension(s) and is
therefore in the extension spec.
The error messages were shortened and no longer include a section
reference. Now the link goes directly to the line in the spec where
the valid usage text occurs. The base of the spec link is the core spec
unless the VU requires an extension in which case the spec with all
extensions is used as the base.
Diffstat (limited to 'scripts/parameter_validation_generator.py')
0 files changed, 0 insertions, 0 deletions