-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[dotnet] Split nuget groups between shipping, test, and the devtools generator #16644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: trunk
Are you sure you want to change the base?
Conversation
|
Thank you, @RenderMichael for this code suggestion. The support packages contain example code that many users find helpful, but they do not necessarily represent After reviewing the change, unless it is a critical fix or a feature that is needed for Selenium We actively encourage people to add the wrapper and helper code that makes sense for them to their own frameworks. |
PR Compliance Guide 🔍Below is a summary of compliance checks for this PR:
Compliance status legend🟢 - Fully Compliant🟡 - Partial Compliant 🔴 - Not Compliant ⚪ - Requires Further Human Verification 🏷️ - Compliance label |
||||||||||||||||||||||||||||||||
PR Code Suggestions ✨Explore these optional code suggestions:
|
||||||||||||
| @@ -1,55 +1,39 @@ | |||
|
|
|||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The benefits of this approach are visible in this file (note the new size of the GROUP nuget section), and in dotnet/paket.nuget.bzl
|
I am not experienced in If it allows |
|
@nvborisenko It does let us use different versions of packages in test vs. source! Who is best to tag for Bazel changes? |
|
Simon Stewart is the best. @shs96c please review briefly whether it follows bazel philosophy. |
User description
Almost all of our dependencies are internal; we can use that to simplify our build process.
🔗 Related Issues
💥 What does this PR do?
🔧 Implementation Notes
💡 Additional Considerations
🔄 Types of changes
PR Type
Enhancement
Description
Split NuGet dependencies into three separate groups: shipping, tests, and devtools generator
Created dedicated Bazel build files for each NuGet package group with separate extensions
Updated paket.dependencies to organize packages by their usage context
Refactored BUILD.bazel files to use group-specific package helper functions
Diagram Walkthrough
File Walkthrough
14 files
New devtools generator NuGet package repository definitionNew Bazel module extension for devtools generator packagesNew test NuGet package repository definitionNew Bazel module extension for test packagesRemoved test and devtools packages from shipping groupReorganized dependencies into three separate groupsUpdated NUnitLite dependency to use tests_nuget groupAdded extensions for tests and devtools generator NuGet groupsUpdated test dependencies to use tests_nuget_package helperUpdated test dependencies to use tests_nuget_package helperUpdated test dependencies to use tests_nuget_package helperUpdated test dependencies to use tests_nuget_package helperUpdated test dependencies to use tests_nuget_package helperUpdated devtools dependencies to use devtools_nuget_package helper2 files
New helper function for test NuGet package referencesNew helper function for devtools NuGet package references1 files