You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is related to the recently merged PR for fiber/v3 the main repo: fiber#3131.
This issue proposes to update the SSE recipe to take advantage of this new v3 feature.
Describe the solution you'd like
This issue is to track updating the call c.Status(fiber.StatusOK).Context().SetBodyStreamWriter(fasthttp.StreamWriter(...)) to instead use c.Status(fiber.StatusOK).SendStreamWriter(...).
We should also update the markdown tutorial as well for SSE.
Describe alternatives you've considered
N/A
Additional context
This update is from a v2->v3 change. It may be a good idea to use a separate migration branch for this change to later merge into master when v3 is officially released.
The text was updated successfully, but these errors were encountered:
I was thinking, should we make a main branch to house all v2->v3 updates (e.g. v3-migration)? This way, we can contain all v3 updates into one simple merge once v3 is officially released.
If not, I can add this make a PR to a separate branch (e.g. v3-migration/sse-using-buffered-streams) and we can merge it directly into master once v3 is released.
Is your feature request related to a problem?
This issue is related to the recently merged PR for fiber/v3 the main repo: fiber#3131.
This issue proposes to update the SSE recipe to take advantage of this new v3 feature.
Describe the solution you'd like
This issue is to track updating the call
c.Status(fiber.StatusOK).Context().SetBodyStreamWriter(fasthttp.StreamWriter(...))
to instead usec.Status(fiber.StatusOK).SendStreamWriter(...)
.We should also update the markdown tutorial as well for SSE.
Describe alternatives you've considered
N/A
Additional context
This update is from a v2->v3 change. It may be a good idea to use a separate migration branch for this change to later merge into
master
when v3 is officially released.The text was updated successfully, but these errors were encountered: