Month-only formatter incorrectly outputs ‘to YEAR’ for same-month ranges in non-current years

Thanks, looks like your MR added these new PHPCS issues.

 260 | ERROR   | [x] Inline comments must end in full-stops, exclamation marks, question marks, colons, or closing
     |         |     parentheses (Drupal.Commenting.InlineComment.InvalidEndChar)
 262 | ERROR   | [x] Inline comments must end in full-stops, exclamation marks, question marks, colons, or closing
     |         |     parentheses (Drupal.Commenting.InlineComment.InvalidEndChar)
 264 | WARNING | [ ] Line exceeds 80 characters; contains 86 characters (Drupal.Files.LineLength.TooLong)
 264 | ERROR   | [x] Comments may not appear after statements (Drupal.Commenting.PostStatementComment.Found)
 264 | ERROR   | [x] Inline comments must end in full-stops, exclamation marks, question marks, colons, or closing
     |         |     parentheses (Drupal.Commenting.InlineComment.InvalidEndChar)

See https://git.drupalcode.org/issue/date_ap_style-3542969/-/jobs/6329113

I went ahead and updated the fork. We fixed all test failures upstream. Now all failures are from this merge request.

@trackleft2 All phpcs issues resolved .

Thank you, how do you feel about adding a phpunit test to cover this change?
I was thinking we could just add the PHPUnit test that was failing and found this bug in the first place.

We changed our PHPUnit tests in this commit to make sure the year was always the current year.

https://git.drupalcode.org/project/date_ap_style/-/merge_requests/26/diffs

If you don't feel comfortable adding a test, I could do it also. However you want to handle it is fine by me.

Hii @trackleft2 , can you please write PHPUnit tests for it , i don't have much idea about them

OK, I've updated your branch, what do you think about the test?

@trackleft2 The test cases looks good to me . RTBC ++