Support complex revision tables in overlay#50
Support complex revision tables in overlay#50AryaHassanli merged 2 commits intoproject-chip:mainfrom
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 significantly enhances the AsciiDoc overlay parsing mechanism to correctly handle conditional content, such as 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. 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 enhances the overlay logic to better support complex conditional structures within tables, particularly for revision history. The changes involve tracking addToCell state across conditional blocks and introducing a new helper function, isContentIfDef, to determine if a conditional block is defining cell content rather than table rows. The logic appears sound. I've added a few comments to clean up the new function by removing unused parameters.
Add support for some complex table structures in overlay.
Using ifdefs in table cells is partially supported now. Here's what works and what doesn't:
Example 1: ✅ What Works (Continuous Directive Flows)
Continuous directives inside an
a|cell behave correctly. They can even be nested under an outer row-levelifdef.ifdefs follow each other consecutively. They aggregate neatly into consecutive block representations without breaking the continuous flow that allows the parser to close the cell.Example 2: ❌ What Breaks (Intercalated Content Breaks)
Interspersing "loose" strings or raw paragraph text between inner block directives inside the cell will cause the table parser to fail.