Megalodon refactor #266
Merged
Megalodon refactor #266
Conversation
This file contains 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
|
Affect by the plemora merge? Or no changes needed? |
Should be able to sling this one after - let me know if you want me to rebase it now you have merged (it was branched from the plemora changes, so should be fine to merge down too) |
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.
Lot of refactoring to move Pixelfed, Mastodon and Pleroma onto a common code structure entirely, removing a LOT of duplication.
This is forked from my Pleroma branch, and should fully support Pleroma with no issues now - as does NOT use the Mastodon compatibility API at all. I've tested this with my own Pleroma test instance and didn't get any issues.
Bump Megalodon to v7; will move to v8 once I have moved misskey off to it's own lib.