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.

Sign up for GitHub

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

Jump to bottom

Use modules in WASM and Python bindings #60

Open
piotr-roslaniec opened this issue Jun 6, 2023 · 0 comments
Open

Use modules in WASM and Python bindings #60

piotr-roslaniec opened this issue Jun 6, 2023 · 0 comments
Labels
API Related to public API good first issue Good for newcomers

Comments

@piotr-roslaniec
Copy link
Contributor

piotr-roslaniec commented Jun 6, 2023 •
edited
Loading

  • Introduce wasm_bindgen(module = "ferveo/nucypher") in order to avoid naming conflicts between umbral.Ciphertext & ferveo.Ciphertext etc., in WASM bindings
  • Instead of relaying on prefixes (FerveoPublicKey, UmbralPublicKey, etc.) make sure that the naming conflicts are avoided by exposing types from their respective modules (ferveo.PublicKey, umbral.PublicKey).
@piotr-roslaniec piotr-roslaniec added good first issue Good for newcomers API Related to public API labels Jun 6, 2023
@piotr-roslaniec piotr-roslaniec changed the title Use modules in WASM bindings Use modules in WASM and Python bindings Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API Related to public API good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@piotr-roslaniec