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

A byname app that needs a module must register the module before itself #77

Open
b1conrad opened this issue Jun 2, 2022 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@b1conrad
Copy link
Member

b1conrad commented Jun 2, 2022

Don't know how to do this.

Two examples:

  1. byu.hr.connect registers a bunch of ACA-Pico rulesets, including modules. But it remains "in charge". This registration happens in these two rules.
  2. com.vcpnews.fav-color should use css3colors as a module, but can't register the module after it is installed, because it would need to use the module.
@b1conrad b1conrad added the enhancement New feature or request label Jun 2, 2022
@b1conrad
Copy link
Member Author

b1conrad commented Jun 2, 2022

We need some way for a byname app to do this kind of thing, and communicate it to app developers.

b1conrad referenced this issue in b1conrad/byname-apps Jun 2, 2022
@windley
Copy link
Member

windley commented Jun 6, 2022

What about a rule in Wrangler that the child could invoke on the parent so that the parent could do it for the child?

@b1conrad
Copy link
Member Author

Have implemented a workaround. The participant can now manually install needed modules before they add a new app.

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

2 participants