Skip to content
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

Add the possibility to set the maximum number of headers #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

3kyro
Copy link
Collaborator

@3kyro 3kyro commented May 15, 2024

@3kyro 3kyro requested review from arybczak and marinelli May 15, 2024 11:32
Copy link
Collaborator

@jonathanjouty jonathanjouty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation looks fine, I'm not sure why GitHub Actions have not run, despite the upstream actions involving a lot of failures, there are several that pass so it would be nice to at least get one ✅

@@ -110,7 +110,6 @@ import qualified Data.Aeson as A

import qualified Data.Traversable as T
import Control.Exception (throw, throwIO, Exception)
import Data.Monoid
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Irrelevant change, we should probably remove this especially if we want to upstream our changes?


-- | The maximum number of header lines.
--
-- @since TODO
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We would need to fix these TODO documentation comments before submitting a PR upstream

@jonathanjouty
Copy link
Collaborator

Right, I had to manually enable actions as this is a forked repository and it could steal something from the Scrive org.
Manual run: https://github.com/scrive/http-client/actions/runs/9097895860

@jonathanjouty jonathanjouty self-assigned this May 15, 2024
Copy link
Collaborator

@jonathanjouty jonathanjouty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually propose to not merge this PR until it is fully ready to be made into an upstream PR, as we can set the source-repository-package.tag in our internal usages regardless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants