[Feature]: Restructure the project so the core passport functionality is a library crate #1

New issue

Closed

opened 2025-10-04 12:47:03 -04:00 by continuist · 2 comments

continuist commented

2025-10-04 12:47:03 -04:00

Owner

Feature Summary

Need to move the core passport functionality (creating, viewing, verifying, etc) into a library crate so it can be used in other contexts such as a web frontend

Problem or Use Case

We need the same exact Passport code to be able to be easily reused in other applications (such as a WASM frontend in the Web browser) so that we don't have to re-implement any of the functionality. This will ensure that there are no mis-alignments and that we are always using the most up-to-date bug-free code in every context.

Proposed Solution

Use a private Cargo registry hosted at git.sharenet.sh and create a library crate called sharenet-passport that can be used in the CLI version of the Passport creator or a frontend browser version. We want to maintain a clean architecture for the library crate as well as the current CLI implementation that uses the library crate.

Alternatives Considered

N/A

Additional Context

We eventually want to create a WASM-based frontend that uses the new sharenet-passport library crate.

Community Guidelines

I agree to follow this project’s Code of Conduct and contribution guidelines.

### Feature Summary Need to move the core passport functionality (creating, viewing, verifying, etc) into a library crate so it can be used in other contexts such as a web frontend ### Problem or Use Case We need the same exact Passport code to be able to be easily reused in other applications (such as a WASM frontend in the Web browser) so that we don't have to re-implement any of the functionality. This will ensure that there are no mis-alignments and that we are always using the most up-to-date bug-free code in every context. ### Proposed Solution Use a private Cargo registry hosted at git.sharenet.sh and create a library crate called sharenet-passport that can be used in the CLI version of the Passport creator or a frontend browser version. We want to maintain a clean architecture for the library crate as well as the current CLI implementation that uses the library crate. ### Alternatives Considered N/A ### Additional Context We eventually want to create a WASM-based frontend that uses the new sharenet-passport library crate. ### Community Guidelines - [x] I agree to follow this project’s Code of Conduct and contribution guidelines.