Support file: protocol in link urls#291
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 comprehensive support for the Highlights
Changelog
Activity
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 adds support for file: protocol in link URLs, which is a valid URI scheme. The changes correctly handle the file: protocol by providing a fallback for the origin, as Node.js's URL parser can return null for file: URLs. Additionally, the PR includes a fix for parsing URLs where the last path segment is not a version string, improving the robustness of the URL parsing logic. The tests have been updated accordingly. I've found a couple of minor issues in the documentation comments that I've pointed out.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @theguild/federation-composition@0.22.1 ### Patch Changes - [#291](#291) [`ec0ef84`](ec0ef84) Thanks [@jdolle](https://github.com/jdolle)! - Support "file:" protocol and non-RFC 3986 in imported "link" url argument - [#282](#282) [`e507fdd`](e507fdd) Thanks [@kamilkisiela](https://github.com/kamilkisiela)! - Fix supergraph `@join__field` emission for Federation v1 `@external` fields and improve override/requires edge-case handling. - Drop Federation v1 `@join__field(external: true)` fields based on key usage in the subgraph instead of aggregated field key usage across subgraphs. - Avoid emitting redundant `@join__field(external: true)` metadata when a field is only required through overridden paths. - Tighten `@join__field` emission around `@override` and interface type fields. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
File protocols are valid RFC 3986 and should be supported. Also adds support for non-RFC 3986 per the federation link spec