Refactor components to function-based syntax

[jknohr]

Refactor components to use function-based syntax instead of class-based syntax.

• Controls.svelte

  • Refactor to use function-based syntax.
  • Replace class-based syntax with function-based syntax.
  • Update event handling to use callback props.

• Graph.svelte

  • Refactor to use function-based syntax.
  • Replace class-based syntax with function-based syntax.
  • Update event handling to use callback props.
  • Replace $props with individual prop declarations.
  • Update reactivity syntax to use $derived and $effect.

Summary by Sourcery

Refactor the Graph and Controls components to use function-based syntax, removing the class-based syntax and updating event handling to use callback props. Update reactivity syntax in Graph to use $derived and $effect.

New Features:

• Implement support for the svelvet-theme attribute on the document element.

Enhancements:

• Replace $props with individual prop declarations in the Graph component.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request refactors the Svelvet components to use function-based syntax instead of class-based syntax. This includes converting the component's state and props to use the new syntax, as well as updating event handling to use callback props.

Class diagram showing the Graph component refactoring

classDiagram
    class Graph {
        +graph: Graph
        +width: number
        +height: number
        +minimap: boolean
        +controls: boolean
        +toggle: boolean
        +fixedZoom: boolean
        +pannable: boolean
        +disableSelection: boolean
        +ZOOM_INCREMENT: number
        +PAN_INCREMENT: number
        +PAN_TIME: number
        +MAX_SCALE: number
        +MIN_SCALE: number
        +selectionColor: CSSColorString
        +backgroundExists: boolean
        +fitView: boolean
        +trackpadPan: boolean
        +modifier: string
        +theme: string
        +title: string
        +drawer: boolean
        +contrast: boolean
        -animationFrameId: number
        -initialDistance: number
        -initialScale: number
        -anchor: object
        -selecting: boolean
        -creating: boolean
        -adding: boolean
        -isMovable: boolean
        -pinching: boolean
        -initialFit: boolean
        -graphDimensions: GraphDimensions
        +onMouseUp()
        +onMouseDown()
        +handleKeyDown()
        +handleScroll()
        +fitIntoView()
    }
    note for Graph "Refactored from class-based to function-based syntax"

Loading

Class diagram showing the Controls component refactoring

classDiagram
    class Controls {
        +increment: number
        +horizontal: boolean
        +onZoomIn: function
        +onZoomOut: function
        +onFit: function
        +onLock: function
        +onHide: function
        +onUnhideAll: function
        -transforms: Graph['transforms']
        -dimensions: Graph['dimensions']
        -locked: Graph['locked']
        -groups: Graph['groups']
        -bounds: Graph['bounds']
        +unhideAll()
        +zoomIn()
        +zoomOut()
        +fit()
        +lock()
    }
    note for Controls "Converted from class-based to function-based component"

Loading

File-Level Changes

Change	Details	Files
Refactor to use function-based syntax.	Replaced class-based syntax with function-based syntax. Updated event handling to use callback props. Replaced $props with individual prop declarations. Updated reactivity syntax to use $derived and $effect.	src/lib/containers/Graph/Graph.svelte
Refactor to use function-based syntax.	Replaced class-based syntax with function-based syntax. Updated event handling to use callback props.	src/lib/components/Controls/Controls.svelte

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @jknohr - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using arrow functions consistently throughout the codebase for better style consistency with the modern function-based approach

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}