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

Publish to idf-component-registry #312

Open
finger563 opened this issue Aug 19, 2024 · 2 comments
Open

Publish to idf-component-registry #312

finger563 opened this issue Aug 19, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@finger563
Copy link
Contributor

Is your feature request related to a problem?

Related to discussion from #310 - there are many people who use the idf component registry both for project / build configuration as well as for discovery. Publishing espp to it would provide another path for them to discover and use it.

Describe the solution you'd like.

Publish it?

Describe alternatives you've considered.

Toiling away in oblivion

Additional context.

No response

@finger563 finger563 added the enhancement New feature or request label Aug 19, 2024
@finger563 finger563 self-assigned this Aug 19, 2024
@finger563
Copy link
Contributor Author

Note: it's probably a good idea to actually set up each component as a separate idf component with the appropriate dependencies. This will also likely necessitate moving the external submodules into the specific component directories. Need to ensure that the idf component registry can handle components which are subdirectories of repositories and which have submodules within them.

@finger563
Copy link
Contributor Author

Somewhat actually related to #284

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