I haven't seen all call sites yet (only the key generation diff is up) so I can't really tell but maybe it's worth revisiting the types and function arguments to have this as clean and consistent as possible.

rebase

update types

In D6993#209859, @tomek wrote:

Do we know how this diff corresponds to https://linear.app/comm/issue/ENG-3322/fix-stale-cache-error-for-olmwasm#comment-d1aabe3d? Maybe this will somehow improve the experience about the path's configuration?

Example usage is in the test plan, unfortunately, it can not be done as elegantly as in olm case - where both web and .wasm file is hosted from the same place.

Reflect changes caused by D7092

reabase

there is more crypto-relatud stuff, making names more exact to easily distinguish

Check if database result is not empty

• update type
• add message type to error message

• update type
• update worker path
• add check

rebase, update const

rebase, make type read-only

Previous types were too general (string instead of current algorithm names). I've updated this to be more precise (like D7023) but with specific types for the entire module - not only AES algorithms.

improve types and move to flow-typed

I still prefer selecting by hand, but this approach is also correct

reabase

improve code readability

Looks great, only one question:
Isn't the gap between the header Choose apps and actual content with apps bigger on design than on the screenshot you provide?