Skip to content

Conversation

@marc-romu
Copy link
Member

Description

This new component base includes several improvements, such as cleaner code, more robust error handling, enhanced type flexibility, improved async processing, and better separation of concerns between component logic and worker implementations.

The changes aim to make the SmartHopper components more modular, maintainable, and extensible while preserving the core functionality of AI-powered Grasshopper components.

Breaking Changes

The new component base is incompatible with previous components. Old components were moved to the new Testing library. Old components were migrated to use the new component base. Functionality could be slightly different from the previous versions.

Testing Done

RH8.15 on Windows.

Checklist

  • This PR is focused on a single feature or bug fix
  • Version in Solution.props was updated, if necessary, and follows semantic versioning
  • CHANGELOG.md has been updated
  • PR title follows Conventional Commits format
  • PR description follows Pull Request Description Template

…ponentBase SolveInstance method and AsyncComponentBase SolveInstance method to base cases on clear states.
…dular and reusable approach - not working yet...
… Base, to work with "Feature request: Store outputs and prevent from recalculating on file open #8"
… defined via SetPersistentOutput on open/save document. Pending debug with complex output trees and data types.
Signed-off-by: Marc Roca-Musach <49920661+marc-romu@users.noreply.github.com>
docs: prepare docs for migration to new component base
refactor(aitextgenerate): moved to old
feat(aitextgenerate): draft of new component using the new component base
…oreasync

fix(componentbase): Restore async functionatily
feat(componentbase): New component base!
@marc-romu marc-romu merged commit f7a1ee2 into main Jan 26, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants