Skip to content

Conversation

@DavidVujic
Copy link
Owner

@DavidVujic DavidVujic commented Feb 13, 2024

Description

Adding a new command: poly deps

Motivation and Context

A bricks overview of the workspace, or an individual project (by appending the --directory option).

A "deps" view can help out anticipating the usages and trigger a thought process about how to separate (or merge) the bricks.

Partially solves #172

Continuing the work on this feature in upcoming Pull Requests, by adding a view for individual bricks: dependency usage and usings just like with the Clojure tooling.

How Has This Been Tested?

✅ CI
✅ Local install and running commands

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

@DavidVujic DavidVujic changed the title Poly deps command feat(poly deps): first version of the new deps command Feb 14, 2024
@DavidVujic DavidVujic marked this pull request as ready for review February 14, 2024 13:31
@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@DavidVujic DavidVujic merged commit 127315f into main Feb 14, 2024
@DavidVujic DavidVujic deleted the poly-deps-command branch February 14, 2024 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants