fix: support TagSpec TLV fields in JSON export/import#408
fix: support TagSpec TLV fields in JSON export/import#408
Conversation
The builder was missing serialization for SkipUnknownTLVTags, StoreUnknownTLVTags, and PrefUnknownTLV fields on TagSpec, meaning these settings were lost during JSON round-trips.
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the JSON serialization and deserialization capabilities for Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly adds support for SkipUnknownTLVTags, StoreUnknownTLVTags, and PrefUnknownTLV fields to the TagSpec for JSON export and import. The changes are well-implemented, following the existing structure of the builder. The addition of TestExportImportTagSpecTLVFields is great as it ensures the new functionality is covered and that the JSON serialization is stable. I have one minor suggestion to improve code clarity.
Use comma-ok pattern instead of nil checks for map lookups in importField. This is more idiomatic Go and provides clearer error messages. Note: importField now returns an explicit error when tag.sort is missing from JSON. Previously it would silently set Sort to nil, but such specs would fail validation in NewComposite/NewMessage anyway.
Summary
SkipUnknownTLVTags,StoreUnknownTLVTags, andPrefUnknownTLVto the builder'stagDummystruct so theseTagSpecfields are preserved during JSON serializationimportFieldandexportTagto read/write these fields, including prefix lookup validation forPrefUnknownTLV