Expose write_node

[jpirnay]

Expose the internal _write_node function to the outer world. Picks up feature request #256

Summary by Sourcery

New Features:

• Expose the internal _write_node function through a new public write_node function.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request exposes the internal _write_node function as a public API by creating a wrapper function called write_node. This change addresses feature request #256.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Expose internal _write_node function as a public API	Create a new function called write_node Implement write_node as a wrapper for the internal _write_node function Pass all parameters from write_node to _write_node	svgelements/svgelements.py

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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 @jpirnay - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider adding documentation for the new write_node function to explain its purpose, parameters, and expected usage.
• The write_node function doesn't return a value. Is this intentional? If so, consider returning the result of _write_node or documenting that it returns None.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 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.}

[sourcery-ai]

issue (bug_risk): The write_node function doesn't return the result of _write_node

This wrapper function calls _write_node but doesn't return its result. This could lead to unexpected behavior if the caller expects a return value. Consider either returning the result of _write_node or reevaluating the necessity of this wrapper function if it's not adding any additional functionality.