json schema: Add enum value descriptions#626
Conversation
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 introduces a significant enhancement to the Highlights
Changelog
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. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a valuable feature allowing users to add descriptions to enum values, which are then incorporated into the generated JSON schema. The implementation correctly defines a new configuration struct rfl::config::enum_descriptions for users to specialize, and integrates this into the schema generation process across JSON, Avro, and Cap'n Proto. For JSON schema, described enums are appropriately translated into a oneOf structure with const and description annotations, enhancing the clarity and usability of the generated schemas. The changes also include necessary updates to internal schema types and a comprehensive test suite that verifies both the schema generation and the continued functionality of serialization/deserialization. The approach is well-designed and robust.
No description provided.