PostScheduleLabel: Updated the component to return a translatable str…

[CoderAbhinav]

Description:

1. Added a prop to return a proper translatable string for post publish panel.
2. This doesn't affect any existing usage of the component.

What?

As mentioned in the #67487 issue, we need to break the string mentioned here

gutenberg/packages/editor/src/components/post-schedule/label.js

Lines 60 to 95 in 7e9e53d

	export function getPostScheduleLabel(
	dateAttribute,
	{ isFloating = false, now = new Date() } = {}
	) {
	if ( ! dateAttribute || isFloating ) {
	return __( 'Immediately' );
	}
	// If the user timezone does not equal the site timezone then using words
	// like 'tomorrow' is confusing, so show the full date.
	if ( ! isTimezoneSameAsSiteTimezone( now ) ) {
	return getFullPostScheduleLabel( dateAttribute );
	}
	const date = getDate( dateAttribute );
	if ( isSameDay( date, now ) ) {
	return sprintf(
	// translators: %s: Time of day the post is scheduled for.
	__( 'Today at %s' ),
	// translators: If using a space between 'g:i' and 'a', use a non-breaking space.
	dateI18n( _x( 'g:i\xa0a', 'post schedule time format' ), date )
	);
	}
	const tomorrow = new Date( now );
	tomorrow.setDate( tomorrow.getDate() + 1 );
	if ( isSameDay( date, tomorrow ) ) {
	return sprintf(
	// translators: %s: Time of day the post is scheduled for.
	__( 'Tomorrow at %s' ),
	// translators: If using a space between 'g:i' and 'a', use a non-breaking space.
	dateI18n( _x( 'g:i\xa0a', 'post schedule time format' ), date )
	);
	}

Such that translators can easily translate the string.
So I have updated the usePostScheduleLabel with a prop for which will be used to identify where we are using this, so that if it's used in the Post Publish Panel, it will return an output which says "It will go live on %s", this allows the translators to translate the string for most of the langugages, providing them better context.

Why?

This was mentioned in the following issue #67487 and also suggested to break the string so it will be easy for translations.

How?

Basically we have broken down the initial string such that now it will be returning a full label with string for the provided post publish panel, while it will work normally for the rest of the instances.

Testing Instructions

1. Go to Posts > Add New
2. Write a new post
3. Schedule it to be published tomorrow
4. See the post-publish panel.

Testing Instructions for Keyboard

Screenshots or screencast

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @CoderAbhinav! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @govindup63.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: govindup63.

Co-authored-by: CoderAbhinav <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: First-time Contributor.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.