-
-
Notifications
You must be signed in to change notification settings - Fork 30
feat: Add phone format properties to resolve issue #441 #475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
chetanupare
wants to merge
4
commits into
AxeWP:develop
Choose a base branch
from
chetanupare:develop
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
abb8f8a
feat: Add phoneFormatProperties field to resolve issue #441
c3b1066
fix: Address coding standards and add changelog entry
da3d808
test: Add international phone format coverage
chetanupare a810704
fix: Use callable descriptions for phone format properties
chetanupare File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| <?php | ||
| /** | ||
| * Object Type - PhoneFormatProperties | ||
| * | ||
| * @package WPGraphQL\GF\Type\WPObject | ||
| * @since @todo | ||
justlevine marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| */ | ||
|
|
||
| declare( strict_types = 1 ); | ||
|
|
||
| namespace WPGraphQL\GF\Type\WPObject; | ||
|
|
||
| /** | ||
| * Class - PhoneFormatProperties | ||
| */ | ||
| class PhoneFormatProperties extends AbstractObject { | ||
| /** | ||
| * Type registered in WPGraphQL. | ||
| * | ||
| * @var string | ||
| */ | ||
| public static string $type = 'PhoneFormatProperties'; | ||
|
|
||
| /** | ||
| * {@inheritDoc} | ||
| */ | ||
| public static function get_description(): string { | ||
| return __( 'Properties of a phone number format, including label, mask, regex, instruction and type.', 'wp-graphql-gravity-forms' ); | ||
| } | ||
|
|
||
| /** | ||
| * {@inheritDoc} | ||
| */ | ||
| public static function get_fields(): array { | ||
| return [ | ||
|
Check failure on line 35 in src/Type/WPObject/PhoneFormatProperties.php
|
||
| 'label' => [ | ||
| 'type' => 'String', | ||
| 'description' => __( 'The display label for the phone format.', 'wp-graphql-gravity-forms' ), | ||
| ], | ||
| 'mask' => [ | ||
| 'type' => 'String', | ||
| 'description' => __( 'The input mask for the phone format (e.g., "(999) 999-9999").', 'wp-graphql-gravity-forms' ), | ||
| ], | ||
| 'regex' => [ | ||
| 'type' => 'String', | ||
| 'description' => __( 'The regex pattern for validating the phone format.', 'wp-graphql-gravity-forms' ), | ||
| ], | ||
| 'instruction' => [ | ||
| 'type' => 'String', | ||
| 'description' => __( 'The instruction text displayed to users for this phone format.', 'wp-graphql-gravity-forms' ), | ||
| ], | ||
| 'type' => [ | ||
| 'type' => 'String', | ||
| 'description' => __( 'The internal type identifier for the phone format.', 'wp-graphql-gravity-forms' ), | ||
| ], | ||
| ]; | ||
| } | ||
| } | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 'international' format has 'mask' and 'regex' set to boolean false, but the PhoneFormatProperties type defines these fields as String (non-nullable). This creates a type mismatch that will cause GraphQL validation errors when international format is used. Consider converting false values to null in the resolver or updating the PhoneFormatProperties type to make these fields nullable (String instead of String!).