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

Automatically detect Containers #60

Closed
dansiegel opened this issue Nov 26, 2019 · 0 comments
Closed

Automatically detect Containers #60

dansiegel opened this issue Nov 26, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@dansiegel
Copy link
Owner

Description

The number of packages to install and manage can become quite insane. Not to mention it's just silly having to specify the container for PrismApplication or ShinyStartup.

Proposal

Instead of installing:

  • Prism.DryIoc.Forms.Extended
    • Prism.DryIoc.Extensions
    • Prism.Forms.Extended
    • Prism.Container.Extensions

We would instead want to install the following anywhere we need the extended bits

  • Prism.Forms.Extended
    • Prism.Container.Extensions

Leaving just

  • Prism.DryIoc.Extensions | Prism.Unity.Extensions

Which could then only be added to the Platform projects if you wanted.

Benefits

  • PrismApplication could live inside Prism.Forms.Extended
  • Both PrismApplication and the PrismStartup for Shiny Support could use a common locator to pull in the container at runtime.
  • It makes it easier to swap out containers
  • Better Extensibility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant