fix(setCookie): allow cookies with the same name but different options

[unite4]

🔗 Linked issue

#598

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves #598

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

Thanks!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ae91fc8) 74.65% compared to head (337b03f) 74.67%.
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #606      +/-   ##
==========================================
+ Coverage   74.65%   74.67%   +0.01%     
==========================================
  Files          47       47              
  Lines        4246     4249       +3     
  Branches      574      571       -3     
==========================================
+ Hits         3170     3173       +3     
  Misses       1061     1061              
  Partials       15       15              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tobiasdiez]

@unite4 @pi0 I'm a bit confused by the semantics of setCookie now. If I call it twice with the same name but different values, I get now two cookies instead of only one with the latest data. This feels counterintuitive. I encountered this in the context of the built-in session functionality. If you call updateSession you get two session cookies: an empty one and one with the updated data.

[frenzzy]

Currently, it is not possible to set custom session data for the first request:

const session = await useSession(...) // Adds set-cookie with empty data
session.update(...)                   // Adds set-cookie with custom data

The response returns two identical set-cookie headers, but it seems the browser uses only the first one.

Related: #705