-
Notifications
You must be signed in to change notification settings - Fork 31
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
Navigation: SPM local package #657
Conversation
- Move that logic into HandleLemmyLinks.
- Declare settings routes that wrap semantic routes as a data value.
- Documentation. - Move some files. - Update tests.
…rom the data that drives the presentation of views. - Add documentation.
- Move some navigation tests over to package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm all for modularisation - I've been meaning to look into it for the API client 👍
Looks like CI/CD tools work as expected: Converting this to a PR. |
Yea! I figured we'd start in a small corner of the project that doesn't really have too many local dependencies. I guess we could create an |
Pull Request Information
About this Pull Request
Moves
Navigation
files into local SPM package:I set this to draft PR because I haven't looked into/thought about how this might impact our current CI/CD tools or whether we need to adjust those tools.
Additional Notes
I did leave out small portions of Navigation (the actual navigation routes that reference the model/middleware layers) because those local packages don't exist yet.