From 95f8e5060138616bcd20bc3c25aae3f08abd17d2 Mon Sep 17 00:00:00 2001
From: Marc Bernard <59966492+mbtools@users.noreply.github.com>
Date: Tue, 18 Nov 2025 10:42:22 -0500
Subject: [PATCH] Add section on checking warnings and errors

Added guidelines for syntax check warnings and errors in ABAP code.
---
 src/development-guide/read-first/guidelines.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/development-guide/read-first/guidelines.md b/src/development-guide/read-first/guidelines.md
index 64ea2e2c2..feb452af1 100755
--- a/src/development-guide/read-first/guidelines.md
+++ b/src/development-guide/read-first/guidelines.md
@@ -46,6 +46,10 @@ abapGit is targeted for [version 7.02](https://help.sap.com/doc/abapdocu_latest_
 
 [abaplint](https://abaplint.org) will automatically check every pull request for language syntax that is compatible with 7.02.
 
+#### Check Warnings and Errors
+
+The goal is to have as few warnings on high, latest ABAP releases as possible, and no errors on low, earliest supported release (i.e. 7.02). See [design decision](https://github.com/abapGit/abapGit/issues/7438#issuecomment-3441285648).
+
 #### Standard Objects
 
 The code must only reference standard SAP objects (classes, interfaces, DDIC types) that exist in version 7.02 and higher. Referencing objects that do *not* exist in 7.02 creates syntax errors and therefore requires using dynamic ABAP. DDIC types that do *not* exist in 7.02 should be replaced by local type definitions.