AppConfigurationEvaluationEvent Schema

[mrm9084]

Separates the unique values that come from App Configuration from those when just using the feature management library.

[Copilot]

Pull Request Overview

This PR separates the app configuration–specific properties from the generic feature evaluation event schema.

• Removes "AllocationId", "ETag", and "FeatureFlagReference" from the base FeatureEvaluationEvent schema.
• Introduces a new AppConfigurationFeatureEvaluationEvent schema that reintroduces these properties with required validations.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
Schema/FeatureEvaluationEvent/FeatureEvaluationEvent.v1.0.0.schema.json	Removed app configuration–specific properties to decouple them from the base schema.
Schema/FeatureEvaluationEvent/AppConfigurationFeatureEvaluationEventv1.0.0.schema.json	Introduced a new schema extending the base and re-adding the removed properties with strict validations.

Comments suppressed due to low confidence (2)

Schema/FeatureEvaluationEvent/FeatureEvaluationEvent.v1.0.0.schema.json:72

• Removing 'AllocationId', 'ETag', and 'FeatureFlagReference' from the base schema could break consumers that rely on them. Please ensure that a migration plan or clear documentation for consumers is provided.

    },

Schema/FeatureEvaluationEvent/AppConfigurationFeatureEvaluationEventv1.0.0.schema.json:9

• [nitpick] Since the base schema no longer includes 'AllocationId', 'ETag', and 'FeatureFlagReference', reconsider whether referencing it via allOf is necessary or if the schema could be simplified by defining only the relevant properties.

      "$ref": "FeatureEvaluationEvent.v1.0.0.schema.json"