envoyproxy / envoyproxy/envoy

split the wasm Context implementation to different class

Open
#36,907 6 comments 0 reactions 0 assignees View on GitHub
area/wasm enhancement no stalebot tech debt
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 22h
Merged PRs (30d)
430

Description

*Title*: *split the wasm Context implementation to different class*

In the WASM implementation, the root context, the http filter context, the network filter context share same class Context. It make the code hard to read or to maintain.

It would be better to split the Context to different class like RootContext, HttpContext, NetworkContext, etc.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.