Mindful Time Tracking: Simplify Your Focus and Boost Productivity Effortlessly.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | open | dependencies | minor | 5.0.2 -> 5.1.0 |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Update | Change | |---|---| | lockFileMaintenance | All locks refreshed |

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | rusqlite | dependencies | minor | 0.30.0 -> 0.31.0 |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | taiki-e/install-action | action | digest | 3ed9916 -> 6943331 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | taiki-e/install-action | action | digest | 3ed9916 -> 6f9c817 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | taiki-e/install-action | action | digest | 3ed9916 -> bd71f12 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | taiki-e/install-action | action | digest | 3ed9916 -> 14422f8 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | taiki-e/install-action | action | digest | 3ed9916 -> 27e3d94 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | ubuntu | github-runner | major | 20.04 -> 22.04 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | EmbarkStudios/cargo-deny-action | action | digest | 2fad080 -> 68cd9c5 |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | insta (source) | dev-dependencies | patch | 1.36.0 -> 1.36.1 | | insta (source) | dependencies | patch | 1.36.0 -> 1.36.1 |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

🤖 New release

• pace_cli: 0.4.1 -> 0.4.2 (✓ API compatible changes)
• pace_core: 0.14.0 -> 0.15.0 (⚠️ API breaking changes)
• pace-rs: 0.12.0 -> 0.13.0 (✓ API compatible changes)

⚠️ pace_core breaking changes

--- failure inherent_method_missing: pub method removed or renamed ---

Description:
A publicly-visible method or associated fn is no longer available under its prior name. It may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.29.1/src/lints/inherent_method_missing.ron

Failed in:
  ActivityStore::new, previously in file /tmp/.tmpgABIhz/pace_core/src/service/activity_store.rs:42

This PR was generated with release-plz.

Overview

As Pace continues to grow and evolve, ensuring high-quality code becomes increasingly critical. This issue aims to address the current gaps in test coverage and testability of the Pace project and its libraries. By focusing on enhancing our testing infrastructure and practices, we can significantly reduce bugs, improve stability, and ensure that new features meet our standards for quality and reliability.

Objectives

• Assess Current Testing Framework: Evaluate the existing testing setup and identify areas for improvement.
• Increase Test Coverage: Identify critical areas of the codebase that are currently under-tested or not tested at all.
• Improve Testability of the Code: Refactor code where necessary to make it more amenable to unit and integration testing.
• Integrate Additional Testing Tools: Explore and integrate tools for coverage analysis, fuzz testing, and other advanced testing methodologies.
• Establish Testing Best Practices: Develop guidelines for writing effective tests and ensuring high-quality code.

Action Items

1. Codebase Audit for Test Coverage

   • [x] Conduct a thorough audit of the current test suite to identify coverage gaps.
   • [x] Create a list of components with insufficient tests.

2. Refactor for Testability

   • [x] Identify and refactor tightly coupled components that hinder testability.

3. Expand Test Suite

   • [x] Write additional unit tests to cover critical logic and functionality.

4. Tooling Integration

   • [X] Set up a code coverage tool (we use cargo-tarpaulin)
   • [x] Evaluate and integrate additional testing tools as needed.

5. Documentation and Guidelines

   • [ ] Document testing best practices and guidelines for contributors.
   • [ ] Include examples of effective tests and common patterns to avoid.

6. Continuous Improvement

   • [ ] Establish a process for regularly reviewing and improving test coverage.
   • [ ] Encourage contributions focused on testing via GitHub issues and pull requests.

Request for Contributions

We welcome contributions from the community to help achieve these objectives. Whether it's writing tests, refactoring for better testability, or improving our testing infrastructure, every contribution counts. If you're interested in helping, please comment on this issue with the areas you'd like to work on, or propose new ideas for enhancing our testing practices.

Conclusion

Improving testability and increasing code coverage are essential steps toward maintaining the Pace project's quality and reliability. With a solid testing foundation, we can confidently continue to develop and expand Pace, knowing that we have the practices and infrastructure in place to ensure its stability and performance.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• [ ] chore(deps): update actions/upload-artifact action to v4

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• [ ] chore(deps): lock file maintenance

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• [ ] chore(deps): update dependency ubuntu to v22

Detected dependencies

• [ ] Check this box to trigger a request for Renovate to run again on this repository

Overview

To further enhance the onboarding experience for new pace users, we propose the addition of a "First Activity Wizard." This interactive guide will walk users through the process of logging their first activity, demonstrating the core functionality of pace and ensuring users are comfortable with the basics of the tool from the outset.

Objectives

• Simplify Initial Learning Curve: Make it easier for new users to understand how to log activities with pace.
• Demonstrate Key Features: Highlight essential features and commands as part of the user's first interaction with the tool.
• Engage Users Immediately: Engage users by having them actively use pace as part of the setup process, improving retention and satisfaction.

Proposed Enhancements

1. Wizard Design and Flow

   • [ ] Design a step-by-step flow for the First Activity Wizard, outlining each step from invoking the wizard to successfully logging the first activity.
   • [ ] Include brief explanations or tips about key features and best practices.

2. Interactive CLI Implementation

   • [ ] Utilize clap, dialoguer, or similar crates to create interactive prompts guiding the user through the activity logging process.
   • [ ] Ensure the wizard is accessible to users with different levels of CLI experience.

3. Validation and Feedback Mechanisms

   • [ ] Implement input validation for each step, providing real-time feedback to guide users in correcting errors.
   • [ ] On successful completion of the wizard, provide positive feedback and suggestions for next steps or additional resources.

4. Documentation and Help Integration

   • [ ] Offer options during the wizard to access more detailed documentation or help for each step.
   • [ ] Include a way to invoke the wizard again in the future, for users who want a refresher.

Request for Comments (RFC)

Feedback and ideas are welcome on several fronts:

• Suggestions for the essential steps and information to include in the First Activity Wizard.
• Ideas for making the wizard engaging and informative without being overwhelming.
• Experiences with similar onboarding tools or wizards in CLI applications that could inform the design of this feature.

Conclusion

The First Activity Wizard is envisioned as a key part of making pace accessible and inviting to new users. By guiding them through logging their first activity, we aim to demystify the process and showcase the simplicity and value of using pace for productivity tracking. This enhancement is about building confidence and competence in new users, setting them up for success with pace.

Overview

While the pace craft setup command has significantly improved the onboarding experience, there's an opportunity to enhance it further by introducing real-time validation for user inputs. This feature aims to ensure that all configuration values provided by users during the setup process are validated on-the-fly, minimizing common configuration errors and streamlining the setup experience.

Objectives

• Enhance User Experience: Provide immediate feedback on configuration inputs to help users correct errors in real-time.
• Reduce Setup Time: Decrease the time users spend on setup by preventing configuration mistakes that require reconfiguration.
• Improve Reliability: Increase the reliability of the pace setup process by ensuring only valid configurations are saved.

Proposed Enhancements

1. Real-Time Input Validation

   • [ ] Implement input validation logic that checks user inputs as they are entered during the setup process.
   • [ ] Provide immediate feedback to users if the input is invalid, along with helpful error messages or suggestions for correction.
   • [ ] Use validator crate

2. Extended Configuration Options

   • [ ] Expand the pace craft setup command to include prompts for additional configuration values, enhancing customization options for users.
   • [ ] Ensure each new configuration option includes specific validation rules based on expected input formats, value ranges, or other criteria.

3. Validation Framework Integration

   • [ ] Integrate or develop a validation framework capable of handling various types of inputs and validation rules.
   • [ ] Allow for easy extension of the validation framework to support future configuration options.

Request for Comments (RFC)

I invite all contributors, especially those with experience in CLI tools and user input validation, to provide their feedback and suggestions on:

• Best practices for implementing real-time validation in command-line interfaces.
• Ideas for additional configuration options that could benefit from real-time validation.
• Recommendations for existing Rust crates or libraries that facilitate input validation and error handling.

Conclusion

By introducing real-time validation for configuration inputs in the pace craft setup command, we aim to make the onboarding process even smoother and more user-friendly. This enhancement will not only save users time by preventing common mistakes but also strengthen the overall reliability of the pace configuration process.