Skip to content

v0.7.0

Latest
Latest

Choose a tag to compare

View all tags
@zakariaf zakariaf released this 15 Jun 05:47
· 3 commits to main since this release
v0.7.0
a502576

🎉 SvgToolbelt v0.7.0 is here! 🎉

This release marks a significant step in the evolution of the library, with the core class and initializer being renamed to SvgToolbelt to better reflect its comprehensive capabilities beyond just zoom and pan. We've also introduced new project planning documents to improve our development process.

✨ Key Changes in v0.7.0:

🚀 Core Renaming: SvgZoom is now SvgToolbelt

  • The main library class SvgZoom has been renamed to SvgToolbelt.
  • The primary initialization function initializeSvgZoom has been renamed to initializeSvgToolbelt.
  • Backward Compatibility: To ensure a smooth transition for existing users, deprecated aliases (SvgZoom and initializeSvgZoom) have been added. These aliases will function as before but will log a console warning encouraging users to update to the new names.

📚 Documentation & Project Structure Updates

  • All documentation, including README.md and MIGRATION.md, has been updated to reflect the new SvgToolbelt naming.
  • Demo examples (demo/index.html, demo/examples/*) have been updated to use the new SvgToolbelt API.
  • Introduced Improvement-Plan.md to outline future development and enhancements.
  • Added Post-Code-Writing-Checklist.md to standardize the development and contribution process.
  • The README.md now includes a "Development" section linking to these new documents.

🧪 Testing Enhancements

  • The entire test suite has been updated to use the new SvgToolbelt naming.
  • New tests have been added to specifically verify the functionality of the deprecated aliases and ensure their console warnings are correctly emitted.

🛠️ Migration

Please refer to the MIGRATION.md file for detailed instructions on updating your projects to use the new SvgToolbelt naming. While the old names will continue to work with a warning, we recommend updating to the new API for future compatibility.

We believe these changes will provide a clearer understanding of the library's purpose and improve the overall development experience. As always, thank you for your support and

Assets 2
Loading