feat: add fedi mod injections to api #6
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
krefsar
force-pushed
the
em/add-mod-injection
branch
from
4b5e43a to
89e47ca
Compare
Contributor
|
will replace this with a more complete updated version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds injections for getting a list of installed mods and installing a mod. Our first use case is for adding mods directly from the catalog mod.
One thing I'm not sure of is, I added the new methods to the LegacyAPI so that it would work in the catalog, which expects to work with the legacy version. I'm open to not updating that legacy api and just forcing the catalog to use a new version of the injections API.