Skip to content

Allow Per-DependencyType default options #42

Open

Description

@RamblingCookieMonster

We currently support PSDependOptions, which specifies global values that apply to all dependencies (unless overridden in individual dependencies).

It might be helpful to add a third layer between these (overrides global, overridden by individual dependencies) for per-dependencytype defaults

Thought someone had mentioned this in an issue, can't seem to find it.

Haven't thought through syntax yet, just getting the idea out there. Off the top of my head without considering existing design or repurcussions, maybe just add keys under PSDependOptions where the key is the dependency type name?

Cheers!

Activity

  1. michaeltlombardi commented on Sep 19, 2017

    @michaeltlombardi
    Contributor

    So, would an example of this be for repositories? The default for the npm type would be.... npm.... but I could override to my own artifactory?

  2. RamblingCookieMonster commented on Sep 19, 2017

    @RamblingCookieMonster
    CollaboratorAuthor

    Yep! Basically... if you have a few different dependency types, and a parameter you want to globally set just for one dependency type, it would be nice to have a middle ground (as is, you can set on each definition or globally - globally will actually work IIRC, just spits out a warning, and if parameters ever share a name with different intent, could be bad).

    Similar to your example, PSGalleryNuget has a Source - other dependency types also use Source, with what likely won't be shared across differing dependency types (assuming they aren't nuget based)

    So right now, I could set the Source to some nuget URI... but what if I also have a few Package types in there, and also want those to have a re-usable (specific to the Package type) Source?

    Plenty of ways to work around it for now, figured at some point it might come in handy though : ) Not on my radar for a while (or until I get bored!)

  3. michaeltlombardi commented on Sep 19, 2017

    @michaeltlombardi
    Contributor

    I think dependency type defaults / overrides is a great idea.

  4. github-actions commented on May 18, 2026

    @github-actions

    This issue has had no activity for 60 days. It will be closed in 30 days unless there is new activity or a maintainer removes the stale label.

  5. github-actions commented on Jun 17, 2026

    @github-actions

    Closing due to inactivity. Please re-open if this is still relevant against the current version.

  6. github-actions commented on Aug 20, 2026

    @github-actions

    This issue has had no activity for 60 days. It will be closed in 30 days unless there is new activity or a maintainer removes the stale label.

  7. added and removed
    status: staleNo activity, candidate for closing
    on Aug 20, 2026
  8. github-actions commented on Oct 20, 2026

    @github-actions

    This issue has had no activity for 60 days. It will be closed in 30 days unless there is new activity or a maintainer removes the stale label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: staleNo activity, candidate for closingtype: enhancementNew feature or improvement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions