• editor/src/messages/frontend/frontend_message.rs
  • Added a tilt field of type f64 to the UpdateDocumentRulers enum variant.
• editor/src/messages/portfolio/document/document_message_handler.rs
  • Included the tilt value from current_ptz.tilt() in the UpdateDocumentRulers message sent to the frontend, defaulting to 0. if the graph view overlay is open.
• frontend/src/components/panels/Document.svelte
  • Introduced a new rulerTilt state variable initialized to 0.
  • Updated the updateDocumentRulers function signature to accept a tilt parameter and assigned it to rulerTilt.
  • Modified the subscription to UpdateDocumentRulers to destructure and pass the new tilt data to updateDocumentRulers.
  • Changed the RulerInput component instantiation to pass originX, originY, and tilt props instead of a single origin prop.
• frontend/src/components/widgets/inputs/RulerInput.svelte
  • Replaced the origin export with originX and originY exports, and added a tilt export initialized to 0.
  • Introduced an Axis interface and new reactive variables (axes, isHorizontal, trackedAxis, otherAxis, stretchFactor, stretchedSpacing, effectiveOrigin) to handle tilt calculations.
  • Added computeAxes and computeEffectiveOrigin functions to determine axis vectors and adjusted origins based on tilt.
  • Refactored computeSvgPath to use effectiveOrigin, stretchedSpacing, and otherAxis for tick rendering, including adaptive minor/micro divisions and tick direction based on tilt.
  • Refactored computeSvgTexts to use effectiveOrigin, stretchedSpacing, and trackedAxis for text rendering, incorporating rotation based on tilt and adaptive label steps.
  • Updated the resize function to use stretchedSpacing for calculating rulerLength.
  • Simplified the mod function by changing remainder to r.
  • Added dominant-baseline attribute to SVG text elements, setting it to central for vertical rulers.
• frontend/src/messages.ts
  • Added a readonly tilt!: number; property to the UpdateDocumentRulers class.

• The pull request description explicitly states "Not meant to be merged", indicating it is likely a work-in-progress or an experimental branch.

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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.