Make Plume compile on release #365
No reviewers
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#365
Loading…
Reference in a new issue
No description provided.
Delete branch "compile-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Remove use of String for body parameters
Create SignedJson and implement FromData for it
Fix #328
Codecov Report
just 👀
@ -44,1 +45,4 @@
self.value()==other.value()
}
pub fn algorithm(&self) -> &str {
i just realised we have a lot of public functions here, but don't document any
@ -44,1 +45,4 @@
self.value()==other.value()
}
pub fn algorithm(&self) -> &str {
Yes, we should do it. Also we should probably use https://git.asonix.dog/asonix/http-signatures instead of rolling our own code
we should also expand our .travis.yml to (test) build
release
Maybe we should just test in release, that's what peoples will use anyway
except for us developers, so, yeah, 👍
I should also update install instructions
Edit: actually documentation already use release, no wonder people where asking for help with installation
Oops I broke code coverage even more I think
Can't complain about low coverage if you don't upload any coverage report 🙃
Just posting this here, as it might be relevant for this pull request:
https://mstdn.nipponalba.scot/@jk/101279615979810008
@marek-lach Thanks! It is indeed related. I responded them.
Thanks!