[brd6]

Description

Adds schema property objects for the three types Notion returns in database and data source schemas that the SDK could not parse:

• VerificationPropertyObject with an empty VerificationPropertyConfiguration;
• UniqueIdPropertyObject with a UniqueIdPropertyConfiguration exposing getPrefix() / setPrefix();
• ButtonPropertyObject with an empty ButtonPropertyConfiguration.

They follow the existing PlacePropertyObject and PhoneNumberPropertyObject shape.

AbstractPropertyObject::getMapClassFromType() now falls back to a new UnsupportedPropertyObject for any type without a property object class, the same way AbstractBlock falls back to UnsupportedBlock. The fallback keeps the property's id, name and type, and getRawData() returns the untouched configuration.

DataSource::toArrayForUpdate() leaves out two more kinds of property. button and verification join the computed types (created_by, created_time, last_edited_by, last_edited_time) in its private read-only list, and every UnsupportedPropertyObject is skipped. Database update payloads are unchanged.

UnsupportedPropertyObjectException is kept for backward compatibility. Nothing throws it any more, so the stale @throws tags on AbstractPropertyObject, DataSource and Database are removed.

Motivation and context

getMapClassFromType() threw UnsupportedPropertyObjectException for every schema type without a matching class. Every wiki database has a verification property, and unique_id and button are common, so DataSource::fromRawData() and Database::fromRawData() threw on those schemas. The exception failed the whole search, dataSources()->retrieve() or databases()->retrieve() result, not just the one property.

Page property values already handle all three types (VerificationPropertyValue, UniqueIdPropertyValue, ButtonPropertyValue); only the schema side was missing.

Once those schemas parse, a retrieved data source can be sent back through dataSources()->update(). The Property object reference says "Button and Verification schemas are response-only", so both join the computed types that data source updates already omit. An unsupported property has no configuration the SDK can vouch for, so it is omitted too. The Update data source properties reference says "Existing properties that you omit stay unchanged". UnsupportedBlock writes no block content back either. One trade-off: a raw array with a mistyped type passed to DataSource::setProperties() is now left out of the update instead of being rejected.

Schema shapes, checked against:

• the Notion API reference, Property object: "verification": {} ("Its schema response has an empty verification object"), "unique_id": { "prefix": "TASK" } ("Its prefix is a string or null"), "button": {} ("A Button property has an empty button object in schema responses");
• the official JavaScript SDK, src/api-endpoints/data-sources.ts (UniqueIdDatabasePropertyConfigResponse: unique_id: { prefix: string | null }) and src/api-endpoints/common.ts (VerificationPropertyConfigurationRequest: verification: EmptyObject, ButtonPropertyConfigurationRequest: button: EmptyObject, UniqueIdPropertyConfigurationRequest: unique_id: { prefix?: string | null }), at makenotion/notion-sdk-js@10aa976.

How has this been tested?

Local commands ran on PHP 8.3 (php:8.3-cli) at 96bb27d, the last commit before main (with #115) was merged in. The merge only touches composer.json, and vendor/bin/phpunit --no-coverage gives the same result at the merge head, 1b43231.

• vendor/bin/phpunit --no-coverage: 310 tests, 2613 assertions, all passing.
• New DataSourceTest::testDataSourceHydratesVerificationUniqueIdAndButtonPropertyConfigurations hydrates a data source whose schema holds verification, unique_id (prefix TASK) and button. It checks that each one maps to its class, reads the prefix, and that toArray() returns each property with the same keys and values Notion sent. Before the change it fails with UnsupportedPropertyObjectException: The given property object "verification" is unsupported.
• New DataSourceTest::testDataSourceHydratesUnknownPropertyTypeAsUnsupportedPropertyObject hydrates a schema with an unknown future_type property. It checks the fallback class, its id, name, type and raw data, that the other properties still hydrate, and that toArrayForUpdate() leaves it out. Before the change it fails with the same exception.
• DataSourceTest::testUpdateSerializationOmitsReadOnlyPropertyConfigurations now also covers verification and button. It failed with Failed asserting that an array does not have the key 'Verification' before they were treated as read-only.
• DataSourceTest::testSetPropertiesRejectsRawArrayWithUnknownType asserted the old exception. It is now testSetPropertiesFallsBackToUnsupportedPropertyObjectForUnknownType and asserts the fallback.
• vendor/bin/phpstan analyse, vendor/bin/psalm --no-cache, vendor/bin/phpcs and vendor/bin/parallel-lint src tests report no errors.
• php -l on every changed file under PHP 7.4 reports no syntax errors.
• CI on this pull request (run 39958783080, head 1b43231): all 21 jobs pass, including Coding standards, Static analysis and Code coverage on PHP 8.1, and Unit tests on PHP 7.4, 8.0 and 8.1 across Ubuntu, macOS and Windows with lowest and highest dependencies.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

PR checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• I have added tests to cover my changes.