Change to using partition

[bouwew]

Should be faster I've been reading

Summary by CodeRabbit

• Refactor
  • Enhanced string processing methods for measurement details and vendor information extraction, improving the accuracy and structure of data handling without altering overall functionality.
• Chores
  • Updated the CHANGELOG to reflect changes in string manipulation techniques, specifically the transition from string.split() to string.partition().

[coderabbitai]

Walkthrough

The changes modify the way string data is processed in the code. In one file, the _power_data_from_modules method now employs the partition method to isolate the first and last elements of a measurement string rather than splitting by underscore. Similar modifications are applied in another file where functions for retrieving vendor names, peak values, and dates have been updated to use partition instead of split. No alterations have been made to the public interfaces or overall control flow.

Changes

Affected Files	Change Summary
plugwise/legacy/.../helper.py	Modified _power_data_from_modules to use partition for creating a measurement list from loc.measurement by selecting only the first and last partitioned elements.
plugwise/.../util.py	Updated get_vendor_name, power_data_peak_value, and skip_obsolete_measurements to replace split with partition for extracting vendor names, peak types, and dates, respectively.
CHANGELOG.md	Added an entry noting the replacement of string.split() with string.partition() under the "Ongoing" section, referencing pull request #702. No other changes to existing entries were made.

Suggested reviewers

• CoMPaTech

Poem

I'm a little bunny, coding late at night,
Swapping splits for partitions with all my might.
Measurements and vendors now hop in clear view,
Data leaping smoothly, fresh as morning dew.
Hoppy code, happy code—yay for changes new! 🐇💻

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e29fa34 and d1d7745.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Check commit

🔇 Additional comments (1)

CHANGELOG.md (1)

6-6: Clear and Concise Changelog Entry

The changelog entry clearly describes the change by stating, “Replace string.split() by string.partition() [#702]”. It succinctly conveys the update and properly references the pull request. If desired, you might consider adding a brief note on the anticipated performance impact for clarity, but as-is, it meets the documentation standards.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (0c6ed90) to head (d1d7745).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #702   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines         3408      3408           
=========================================
  Hits          3408      3408           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.