Cookie parser

[joey1123455]

Description

Implemented a cookie parser, following the same convention used by BodyParser and QuerryParser context methods.
The parser is a context method which takes a struct pointer as argument and assigns all passed cookies to the relevant fields. It returns an error if any.

The feature was requested as an issue, and provides an easier way to handle multiple cookies, and improves developer experience and development time.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Checklist:

• For new functionalities I follow the inspiration of the express js framework and built them similar in usage
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation - /docs/ directory for https://docs.gofiber.io/
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• If new dependencies exist, I have checked that they are really necessary and agreed with the maintainers/community (we want to have as few dependencies as possible)
• I tried to make my code as fast as possible with as few allocations as possible
• For new code I have written benchmarks so that they can be analyzed and improved

Commit formatting:

Use emojis on commit messages so it provides an easy way of identifying the purpose or intention of a commit. Check out the emoji cheatsheet here: https://gitmoji.carloscuesta.me/

[welcome]

Thanks for opening this pull request! 🎉 Please check out our contributing guidelines. If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

[joey1123455]

the issue for this pull request is
🚀 [Feature]: CookieParser #2639
#2639 (comment)

[joey1123455]

@ReneWerner87 Hello, I would like to know what needs to be done before a PR is approved.

[ReneWerner87]

Currently everything we need is there
However, we are still discussing internally and since it is vacation time it is currently a bit slower

[joey1123455]

@ReneWerner87 hello Rene, I noticed some checks failed. Is there anything I need to do?

[ReneWerner87]

Yes, pls check the lint errors

[ReneWerner87]

[joey1123455]

I'll fix all the issues tonight

…

On Wed, 11 Oct 2023, 8:09 am RW, ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/7063188/274173311-5a82d2a4-97af-4f15-bb44-ccd2dd3a58f1.png> — Reply to this email directly, view it on GitHub <#2656 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A25NWE4ID4XXWCSUFU6JBMTX6ZAZDAVCNFSM6AAAAAA5TMYTE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJWHE4DOOJQGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[joey1123455]

Sorry for disturbing you, but I'm trying to confirm the last error I just need to add a test for the returned value? @ReneWerner87

[ReneWerner87]

Sorry for disturbing you, but I'm trying to confirm the last error I just need to add a test for the returned value? @ReneWerner87

yes should be
but would recommend you to watch the binary locally via act or direct

https://github.com/nektos/act

act -W ./.github/workflows/linter.yml

[joey1123455]

Sorry for disturbing you, but I'm trying to confirm the last error I just need to add a test for the returned value? @ReneWerner87

yes should be but would recommend you to watch the binary locally via act or direct

https://github.com/nektos/act

act -W ./.github/workflows/linter.yml

this is the test i wrote for it and i have other tests for the return value as well

[ReneWerner87]

[ReneWerner87]

bb026a6 fixed

[welcome]

Congrats on merging your first pull request! 🎉 We here at Fiber are proud of you! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord