Compression updates v2

[jaytist]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines.
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
compression updates

[codecov]

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (1a04130) compared to base (c877fb0).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #511   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         6    +1     
  Lines          319       341   +22     
=========================================
+ Hits           319       341   +22     

Impacted Files	Coverage Δ
packages/test-suite/src/compression.js	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[jaredwray]

@alphmth - how would we separate this out so that serialize, deserialized could exist without being part of the compression package or maybe an option that if those functions exist we use it otherwise we use what is set?

[jaytist]

@alphmth - how would we separate this out so that serialize, deserialized could exist without being part of the compression package or maybe an option that if those functions exist we use it otherwise we use what is set?

@jaredwray In the set or get method we are using serialize and deserialize methods. To make compression work we need to add compress/decompress method in the serialize/deserialize method. If we make them optional how we will use compression in main keyv project?

[jaredwray]

@alphmth - this is starting to come together. One other thought is to create another export of the test-suite library that does validation of the compression packages so third parties can do that. Can you add that in?

[jaytist]

@jaredwray do we need to add serialize/deserialize as optional? In that case, the user will have to use compress/decompress methods like this

const gzip = new KeyvGzip(); 
const compressedValue = gzip.compressed(value);
const keyv = new Keyv({store: new Map()});
await keyv.set('test-key', compressedValue, 1000);

//get compressed value
const decompressedValue = await gzip.decompressed(await keyv.get('test-key));

[jaredwray]

@jaredwray do we need to add serialize/deserialize as optional? In that case, the user will have to use compress/decompress methods like this

const gzip = new KeyvGzip(); 
const compressedValue = gzip.compressed(value);
const keyv = new Keyv({store: new Map()});
await keyv.set('test-key', compressedValue, 1000);

//get compressed value
const decompressedValue = await gzip.decompressed(await keyv.get('test-key));

Lets go with the current architecture for right now and then will take feedback.

verified