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

feat: in-memory state store components #327

Merged
merged 8 commits into from
Nov 22, 2021

Conversation

seeflood
Copy link
Member

@seeflood seeflood commented Nov 22, 2021

What this PR does:
Add an in-memory state store component;
Modify wasm documents;

Which issue(s) this PR fixes:

See #67 (comment)

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


@codecov
Copy link

codecov bot commented Nov 22, 2021

Codecov Report

Merging #327 (2d7c145) into main (874f546) will not change coverage.
The diff coverage is n/a.

❗ Current head 2d7c145 differs from pull request most recent head 797212d. Consider uploading reports for the commit 797212d to get more accurate results
Impacted file tree graph

@@           Coverage Diff           @@
##             main     #327   +/-   ##
=======================================
  Coverage   56.90%   56.90%           
=======================================
  Files          48       48           
  Lines        2100     2100           
=======================================
  Hits         1195     1195           
  Misses        774      774           
  Partials      131      131           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 874f546...797212d. Read the comment docs.

@seeflood seeflood merged commit 1ac4c06 into mosn:main Nov 22, 2021
@seeflood seeflood deleted the in_memory_components branch November 22, 2021 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants