Do not display Id or Updated metatags

[rprouse]

Fixes #76

Summary by CodeRabbit

• New Features

  • Improved parsing and representation of task items, enhancing handling of project and context tags.
  • Metadata filtering to exclude "id:" and "updated:" tags from display in task representations.

• Bug Fixes

  • Refined equality checks for task items to ensure accurate comparisons.

• Tests

  • Added new tests to verify that specific metadata is excluded from task output, enhancing overall test coverage.

• Chores

  • Updated project version from 0.6.0 to 0.6.1.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to the TaskItem class to enhance the parsing and representation of task items, particularly focusing on the handling of project and context tags. A new method, DisplayMeta, filters out specific metadata tags during string representation. The project file is updated to a new version number, and additional tests are added to verify the exclusion of certain metadata in the output.

Changes

Files	Change Summary
src/todo.domain/Entities/TaskItem.cs	Modified the TaskItem class, updated the Parse and ToColorString methods, and added DisplayMeta.
src/todo/todo.csproj	Updated project version from 0.6.0 to 0.6.1.
tests/todo.tests/Domain/Entities/TaskItemTests.cs	Added new test method DoesNotIncludeIdOrUpdatedMeta to verify metadata exclusion in ToColorString.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TaskItem
    participant TaskItemTests

    User->>TaskItem: Parse task description
    TaskItem->>TaskItem: Identify tags (projects, contexts)
    TaskItem->>TaskItem: Call DisplayMeta
    TaskItem-->>User: Return formatted task string
    User->>TaskItemTests: Run tests
    TaskItemTests->>TaskItem: Verify output does not include "id" or "updated"

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Do not display id or updated tags (#76)	✅

🐇 In the garden, tasks do bloom,
No "id" or "updated" to consume.
With colors bright, they dance and play,
A tidy list for every day!
Hopping through code, oh what a sight,
Celebrating changes, all feels right! 🌼

---

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 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 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.