Skip to content

Conversation

@toumorokoshi
Copy link
Member

@toumorokoshi toumorokoshi commented Oct 5, 2025

Filling some gaps in the guidance to clarify what to do if fields are not present. As well as if fields are not present.

Fixes #123.

🍱 Types of changes

What types of changes does your code introduce to AEP? Put an x in the boxes
that apply

  • Enhancement
  • New proposal
  • Migrated from google.aip.dev
  • Chore / Quick Fix

📋 Your checklist for this pull request

Please review the AEP Style and Guidance for
contributing to this repository.

General

💝 Thank you!

@toumorokoshi toumorokoshi requested a review from a team as a code owner October 5, 2025 05:20
Filling some gaps in the guidance to clarify what to do if 
fields are not present. As well as if fields are not 
present.

Fixes aep-dev#241.
@toumorokoshi toumorokoshi changed the title fix(137): clarify behvavior (field presence and errors). fix(137): clarify behavior (field presence and errors). Oct 5, 2025
@toumorokoshi toumorokoshi merged commit 0ad7a8b into aep-dev:main Oct 5, 2025
3 checks passed
@github-project-automation github-project-automation bot moved this to Done in aep-2026 Oct 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Consider removing allow_missing in update requests in favor of Apply/PUT

2 participants