- Introduced initialization of sync services for libraries that were loaded before the networking service became available, ensuring all libraries can utilize synchronization capabilities.
- Enhanced logging to provide detailed information on the sync service initialization process, including warnings for any failures encountered during setup.
- Removed the obsolete test_extension_beautiful.wasm file to clean up the project structure.
- Introduced a new `ExtensionJobRegistry` to manage custom job types for extensions at runtime.
- Added `host_register_job` function to facilitate job registration from WASM extensions.
- Updated `PluginEnv` and `PluginManager` to include job registry functionality.
- Enhanced the `job` macro to support automatic job registration during plugin initialization.
- Updated documentation and tests to reflect the new job registration capabilities.
- Replaced all instances of the `spacedrive_job` macro with the simplified `job` macro across documentation and code files.
- Updated related documentation to reflect the new macro name, enhancing clarity for developers.
- Ensured all examples and usage instructions are aligned with the updated macro terminology.
- Renamed `spacedrive_job` macro to `job` for clarity and consistency across the SDK.
- Updated references in the SDK and test extension to reflect the new macro name.
- Enhanced comments in the test extension to better describe functionality and usage.
- Added "checkpointing" to the cspell project words for improved spell checking.
- Added a new SDK for developing Spacedrive WASM extensions, featuring a type-safe API and comprehensive documentation.
- Implemented core components including job context management, FFI bindings, and error handling mechanisms.
- Created macros for simplifying extension and job definitions, enhancing developer experience.
- Included detailed README and status documentation to guide users in utilizing the SDK effectively.
- Updated Cargo configurations for the SDK and its macros, ensuring proper dependency management and build processes.
- Introduced `IT_WORKS.md` to document the successful execution of the WASM extension system, detailing test results and the steps taken during the process.
- Updated the `wasm_extension_test.rs` to reflect changes in the test extension structure, ensuring accurate loading and verification of the new test extension.
- Refactored the `Cargo.toml` files for both the SDK and test extension to streamline dependencies and improve build configurations.
- Removed the obsolete `test-extension-minimal` directory, consolidating the extension structure for better clarity and maintenance.
- Enhanced the `JobContext` implementation to utilize byte arrays for UUIDs, improving memory handling and consistency across the extension system.
- Documented next steps for further development, including the creation of a WasmJob executor and additional testing for job dispatching.
- Introduced `CURRENT_STATUS.md` to outline the current state of the WASM extension system, detailing what is working and what remains to be addressed.
- Documented the implementation status of core components, including the `PluginManager`, host functions, and test structure.
- Highlighted immediate tasks and timelines for further development, providing a clear path forward for the extension system.
- Updated the `Core` struct to include the `plugin_manager`, ensuring proper initialization during the core setup.
- Created integration tests for loading WASM extensions, validating the functionality of the new system.
- Implemented a complete WASM extension framework, enabling secure, sandboxed plugins.
- Added core components including `PluginManager`, `host_functions`, and `permissions` for managing the lifecycle and security of extensions.
- Integrated Wasmer runtime for executing WASM modules, enhancing the platform's extensibility.
- Developed a demo extension showcasing the new API, significantly reducing boilerplate code and improving developer experience.
- Updated documentation to reflect the new architecture and provide guidance for extension development.
- Prepared for testing and validation of the extension system, marking a significant step towards a robust plugin ecosystem.
