Add __isset magic method to FileMakerRelation for field existence checks#160
Merged
msyk merged 1 commit intoJul 15, 2026
Merged
Conversation
Co-authored-by: Junie <junie@jetbrains.com>
Owner
|
@ProgrammiererEFZ and @junie-agent , Thanks for committing good feature. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary: This pull request adds support for the PHP
isset()function when checking for fields or portals on a record object (FileMakerRelation).Changes:
__issetmagic method insrc/Supporting/FileMakerRelation.php.field()method to verify if a field or portal exists.trueif the field exists and false if it does not (handling theExceptionthrown byfield()).Reasoning: Currently, the library supports magic property access via
__get, but callingisset($record->field_name)always returns false because__issetwas not implemented. This change makes the API more intuitive and consistent with standard PHP object behavior, allowing developers to safely check for field existence before access.