feat: improve TypeScript type definitions with optional parameters #665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR improves the TypeScript type definitions for jsMind by making most configuration options optional, which provides better developer experience and matches the actual usage patterns shown in the official documentation.
Changes Made
Type Definition Improvements
New Type Support
Documentation & Testing
Benefits
Breaking Changes
Testing
Related Issues
This addresses the need for more flexible TypeScript type definitions that better represent the actual API usage patterns.
Checklist