internal imports by default, only enable warnings as errors in CI#112
internal imports by default, only enable warnings as errors in CI#112tayloraswift merged 1 commit intomasterfrom
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 refactors the Swift package configuration to adopt the 'InternalImportsByDefault' feature, enhancing module encapsulation and preparing for future Swift language evolution. It also introduces conditional compilation for treating specific warnings as errors, enabling stricter checks in CI while providing flexibility for local development. Highlights
Changelog
Ignored Files
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 enables the InternalImportsByDefault Swift feature and configures warnings to be treated as errors only in CI environments. The changes correctly adjust import statements across various modules to be either internal or public as needed, and the CI script is updated to enable warnings as errors. My review includes one suggestion in Package.swift to simplify the logic for checking the environment variable, improving code readability.
| switch ProcessInfo.processInfo.environment["WARNINGS_AS_ERRORS"] { | ||
| case "true"?: true | ||
| case "1"?: true | ||
| default: false | ||
| } |
There was a problem hiding this comment.
The logic for checking the WARNINGS_AS_ERRORS environment variable can be simplified for better readability and conciseness. Using a direct boolean comparison is more idiomatic and easier to understand than a switch statement on an optional value.
let value = ProcessInfo.processInfo.environment["WARNINGS_AS_ERRORS"]
return value == "true" || value == "1"
No description provided.