-
Notifications
You must be signed in to change notification settings - Fork 13
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
Do not filter out parameters with the same name in pagination links #41
Conversation
@pbrisbin feel free to take a look at this when time permits. I also left a few comments above. FYI: I'm on GHC 8.10.7 and couldn't test this using GHC 9.0.2, if this causes any issues I'll try to get 9.0.2 up and running. |
57545fd
to
085ec10
Compare
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.
This is great, thank you.
Can you go ahead and bump the minor version in |
085ec10
to
78c829a
Compare
78c829a
to
8ab6082
Compare
@pbrisbin I went with the approach of exporting the parameter filtering function to simplify the spec and left a few comments above regarding things I'm unsure of, it'd be nice if you could take a look. |
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.
Thanks for your continued efforts here, I requested some minor changes.
Co-authored-by: patrick brisbin <[email protected]>
67bf5c8
to
21d4606
Compare
21d4606
to
7954604
Compare
9b29f4c
to
42c4958
Compare
42c4958
to
4537442
Compare
@pbrisbin I took another look at this and tried to clean up the conversation above a bit. I couldn't come up with property tests for everything but added a couple of property tests, unit tests and left a few comments. Not sure if the CI failure is related to this. Feel free to take a look when time permits and let me know if I've missed anything or if you have any questions! |
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.
This looks good overall, thanks! There are just a few organizational things I noted, but I'm willing to just fix that up myself and push to this PR before merging, if you prefer. Let me know!
@pbrisbin thanks for the feedback, I think all issues should be addressed! |
Awesome. I set this to auto-merge on green, which will auto-release to Hackage. Thanks! |
@pbrisbin there are two CI jobs failing which I'm not sure if they're relevant or not: CI / test (stack.yaml) and restyled. If you have the time to take a look that'd be great. |
Just for future reference: if the PR check is Required, it's, well, required. Otherwise, it's not. So let's ignore Restyled for now and look at the main test. It looks like a new diff --git i/.github/workflows/ci.yml w/.github/workflows/ci.yml
index 95effd4..58b08c8 100644
--- i/.github/workflows/ci.yml
+++ w/.github/workflows/ci.yml
@@ -47,6 +47,8 @@ jobs:
- if: ${{ matrix.stack-yaml == 'stack.yaml' }}
uses: freckle/weeder-action@v1
+ with:
+ weeder-version: 2.3.0
hlint:
runs-on: ubuntu-latest |
Head branch was pushed to by a user without write access
Missed the |
Wow yeah, still down. I'll keep an eye on the status page and re-run when it's back up. |
Fixes #40