Skip to content

Fix: Correct action_past_tense assignment in ContentProcessor - #413

Open
prjanitor wants to merge 1 commit into
moremoban:devfrom
prjanitor:prjanitor/b004a7d756773a68618d9e56944809a0b020e1d6
Open

prjanitor wants to merge 1 commit into
moremoban:devfrom
prjanitor:prjanitor/b004a7d756773a68618d9e56944809a0b020e1d6

Conversation

@prjanitor

Copy link
Copy Markdown

Bug Description

In ContentProcessor.__init__, self.action_past_tense was incorrectly assigned self.action_continuing_tense instead of the action_past_tense parameter, causing the past tense to always equal the continuing tense.

Fix

Changed line 24 from:

self.action_past_tense = action_continuing_tense

to:

self.action_past_tense = action_past_tense

Impact

This ensures that the past tense action string is correctly stored and used when displaying template processing status messages.


This PR was generated by PRJanitor — an automated tool that finds and fixes small bugs in open-source projects.

We respect your contribution guidelines — if your project doesn't accept bot PRs, we won't send more. You can also add a .github/prjanitor.yml file with enabled: false to opt out explicitly.

In ContentProcessor.__init__, self.action_past_tense was incorrectly assigned
self.action_continuing_tense instead of the action_past_tense parameter.
This caused the past tense to always equal the continuing tense.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes a bug in ContentProcessor.__init__ where the action_past_tense instance attribute was mistakenly assigned from action_continuing_tense, causing status/reporting strings to use the wrong tense.

Changes:

  • Correctly assign self.action_past_tense from the action_past_tense parameter.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants