Skip to content

Conversation

@laurelfulford
Copy link
Contributor

@laurelfulford laurelfulford commented Jan 6, 2026

All Submissions:

Changes proposed in this Pull Request:

I noticed this while working on something else:

The Donate block has a new per month/per year frequency text in the "Other" field label, but there's no space before this label in the editor. This PR fixes that.

How to test the changes in this Pull Request:

  1. Add the Donate block to the editor and pick the Monthly or Annually tab; adjust it so you can see the 'Other' field, and note the text:
CleanShot 2026-01-06 at 10 44 18
  1. Apply this PR and run npm run build.
  2. Refresh the editor and confirm the text is properly spaced:
CleanShot 2026-01-06 at 10 46 18

Other information:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your changes, as applicable?
  • Have you successfully ran tests with your changes locally?

@laurelfulford laurelfulford marked this pull request as ready for review January 6, 2026 19:02
@laurelfulford laurelfulford requested a review from a team as a code owner January 6, 2026 19:02
_x( 'per %s', 'per `Frequency`', 'newspack-blocks' ),
frequencySlug
);
: ' ' +
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, I wonder if this is friendly for all languages? I'm just guessing there might be languages where forcing the frequency string to come after the amount string will result in some potentially funky translations.

Maybe it would be better to add the frequency within the getFormattedAmmount method below so we can generate these translated strings consistently?

WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

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

I realize this is the case already before this PR, so I'll go ahead and approve. But I do think this is a good chance to address this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @chickenn00dle!

Hmm, I wonder if this is friendly for all languages? I'm just guessing there might be languages where forcing the frequency string to come after the amount string will result in some potentially funky translations.

Yeah, that's a good call! I made myself a separate issue to look at this a little closer (NPPM-2509) 🙂 I also see there's a separate getFrequencyLabelWithAmount const that possibly has the same missing space issue (and order issue - I'm not sure yet! This is the first time I've noticed this change).

@laurelfulford laurelfulford merged commit d18cf42 into trunk Jan 6, 2026
14 checks passed
@laurelfulford laurelfulford deleted the fix/add-space branch January 6, 2026 20:12
@github-actions
Copy link

github-actions bot commented Jan 6, 2026

Hey @laurelfulford, good job getting this PR merged! 🎉

Now, the needs-changelog label has been added to it.

Please check if this PR needs to be included in the "Upcoming Changes" and "Release Notes" doc. If it doesn't, simply remove the label.

If it does, please add an entry to our shared document, with screenshots and testing instructions if applicable, then remove the label.

Thank you! ❤️

matticbot pushed a commit that referenced this pull request Jan 9, 2026
# [4.21.0-alpha.1](v4.20.1...v4.21.0-alpha.1) (2026-01-09)

### Bug Fixes

* add Link to express payment array ([#2266](#2266)) ([fdd6fd5](fdd6fd5))
* add space to donate block label in editor ([#2270](#2270)) ([d18cf42](d18cf42))

### Features

* improve express checkout handling by surfacing errors ([#2273](#2273)) ([1d98b9b](1d98b9b))
@matticbot
Copy link
Contributor

🎉 This PR is included in version 4.21.0-alpha.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants