feat(server): allow named url shortening (#40)#373
Conversation
|
Thanks for the PR. Can you also please add test cases and fixtures? |
00153af to
ca2ff07
Compare
|
Sure thing! I'm trying to get in lint compliance too. |
|
There are a few things to fix. The formatting checks, lints, and tests fail. These have to be fixed and new tests should be added that handle your use case. |
6fdb015 to
d718a84
Compare
tessus
left a comment
There was a problem hiding this comment.
Unfortunately there are still issues with this PR.
May I suggest to go through the checklist?
cargo fmt --check --cargo clippycargo test -- --test-threads 1./fixtures/test-fixtures.sh
Currently the code does not even compile.
d718a84 to
c9c0614
Compare
|
I've pushed an update now, it passes CI on my own fork. I've also updated the checkboxes in the original message with what I've done. |
tessus
left a comment
There was a problem hiding this comment.
Nice, this looks good. Thanks.
|
@orhun can you please have a look? I promised I would only merge dependency PRs. ;-) @Vaelatern let's wait for orhun's approval, since he's the owner of the project. I can't merge without his ok. |
|
Sounds good! I just started using this today, noticed this hole, and wanted to contribute a fix. |
|
Apparently I need to sign the commits too |
|
why? nope, you don't. This project does not have a requirement of signed commits. |
|
oops, yeah. I am sorry. this policy must be new. |
c9c0614 to
e390f46
Compare
|
Now pushed with signed commit, both this and #374 (which I'm about to refactor a tiny bit) |
|
Thanks. P.S.: We squash the commits in a PR anyway, in which case the resulting commit would be signed, so the message under the merge button was a bit confusing and IMO wrong. It should say that all commits in the PR must be signed. |
Description
I ran the filename header through the URL shortening route
Motivation and Context
This lets me use rustypaste to link to a specific link using a specified short name (for ergonomics).
Also fixes #40 by the by.
How Has This Been Tested?
Changelog Entry
-->
Types of Changes
Checklist: