Skip to content
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

Add --only option to sharezone cli. #1292

Merged
merged 1 commit into from
Feb 8, 2024
Merged

Conversation

Jonas-Sander
Copy link
Collaborator

@Jonas-Sander Jonas-Sander commented Feb 7, 2024

The option allows to run a ConcurrentCommand only for the specified package names.

E.g.: sz analyze --only sz_repo_cli, sz test sharezone,abgabe_client_lib.

Summary by CodeRabbit

  • New Features
    • Introduced an option to execute tasks for specific packages only, enhancing task management efficiency.

The option allows to run a `ConcurrentCommand` only for the specified package names.

E.g.: `sz analyze --only sz_repo_cli`, `sz test sharezone,abgabe_client_lib`.
Copy link
Contributor

coderabbitai bot commented Feb 7, 2024

Walkthrough

The recent update introduces a new feature within the CLI tool, allowing users to target specific packages for task execution through the introduction of an only option. This enhancement filters the packages to be processed, ensuring that tasks are only run for those explicitly specified, thereby streamlining operations and improving efficiency for developers working in multi-package environments.

Changes

File Path Change Summary
.../concurrent_command.dart - Added only option to target specific packages.
- Updated packagesToProcess to filter based on the only option.

🐇🌟

In the land of code where the snippets roam free,
A clever little update, as nifty as can be.
With an only option, tasks are now concise,
Making our coding journey oh, so nice.
🎉🐰

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Status

Actionable comments generated: 3

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between a38bed9 and cc03228.
Files selected for processing (1)
  • tools/sz_repo_cli/lib/src/common/src/concurrent_command.dart (2 hunks)

Comment on lines +18 to +22
..addOption(
'only',
help:
'Only run the task for the given package(s). Package names can be separated by comma. E.g. `--only package1` or `--only=package1,package2`.',
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure the description for the --only option is clear and concise. Consider mentioning the expected behavior when no package names are provided.

Comment on lines +62 to +72
Stream<Package> get packagesToProcess {
var stream = repo.streamPackages();

final onlyPackageNames = _parseOnlyArg();
if (onlyPackageNames.isNotEmpty) {
stream =
stream.where((package) => onlyPackageNames.contains(package.name));
}

return stream;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The implementation of filtering packages based on the --only option in packagesToProcess is correct. However, consider the performance impact of calling stream.where inside an if statement. For large repositories, this could introduce a delay. Evaluate if there's a more efficient way to filter the packages, possibly by pre-processing the list before converting it to a stream.

Comment on lines +74 to +80
List<String> _parseOnlyArg() {
final onlyArg = argResults!['only'] as String?;
if (onlyArg == null) {
return [];
}
return onlyArg.split(',');
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The _parseOnlyArg method correctly parses the --only argument. However, it does not trim whitespace from the package names after splitting. This could lead to unexpected behavior if users include spaces after commas. Add trimming to ensure robustness.

- return onlyArg.split(',');
+ return onlyArg.split(',').map((name) => name.trim()).toList();

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
List<String> _parseOnlyArg() {
final onlyArg = argResults!['only'] as String?;
if (onlyArg == null) {
return [];
}
return onlyArg.split(',');
}
List<String> _parseOnlyArg() {
final onlyArg = argResults!['only'] as String?;
if (onlyArg == null) {
return [];
}
return onlyArg.split(',').map((name) => name.trim()).toList();
}

Copy link
Member

@nilsreichardt nilsreichardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nilsreichardt
Copy link
Member

Nice! We can also update the CI pipelines

@Jonas-Sander Jonas-Sander added this pull request to the merge queue Feb 8, 2024
@Jonas-Sander
Copy link
Collaborator Author

Nice! We can also update the CI pipelines

Which jobs do you mean exactly where this would be useful?

github-merge-queue bot pushed a commit that referenced this pull request Feb 8, 2024
… automatically applied. (#1293)

Use `super.packagesToProcess` so that #1292 also applies to `sz test`
Merged via the queue into main with commit 8beb894 Feb 8, 2024
26 checks passed
@Jonas-Sander Jonas-Sander deleted the sz-cli-only-option branch February 8, 2024 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants