# Allowlist for xml_consistency_check.py
#
# Each non-comment, non-blank line is the exact text of a warning to suppress
# from the failure total used by --exception. Allowlisted warnings are still
# printed but we don't throw on them. These are warnings that can not be fixed
# in the short term but should be addressed eventually.
#
# To allow a new warning, copy its line verbatim from the script output.

# --- Pre-existing warnings (not fixable in the short term) ---
common.xml: Enum: CAMERA_TRACKING_STATUS_FLAGS bitmask should not contain 0
common.xml: Message GIMBAL_DEVICE_INFORMATION field cap_flags enum GIMBAL_DEVICE_CAP_FLAGS does not fit in type: uint16_t

# --- Live messages referencing deprecated enums ---
common.xml: Message HIL_CONTROLS field mode enum MAV_MODE is deprecated

# --- Superseded commands referencing deprecated enums ---
# Both are <superseded/> rather than <deprecated/> and say they are still usable
# with legacy gimbals, so the reference to MAV_MOUNT_MODE is intentional.
common.xml: Command MAV_CMD_DO_MOUNT_CONFIGURE param 1 enum MAV_MOUNT_MODE is deprecated
common.xml: Command MAV_CMD_DO_MOUNT_CONTROL param 7 enum MAV_MOUNT_MODE is deprecated

# --- Command params with small integer ranges (no enum defined yet) ---
common.xml: Command MAV_CMD_NAV_CONTINUE_AND_CHANGE_ALT param 1 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_NAV_LOITER_TO_ALT param 4 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_DO_FOLLOW param 4 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_NAV_PATHPLANNING param 1 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_NAV_PATHPLANNING param 2 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_CONDITION_YAW param 3 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_DO_FLIGHTTERMINATION param 1 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_DO_CONTROL_VIDEO param 2 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_DO_CONTROL_VIDEO param 4 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_DO_FENCE_ENABLE param 1 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_PREFLIGHT_CALIBRATION param 1 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_PREFLIGHT_CALIBRATION param 4 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_PREFLIGHT_CALIBRATION param 6 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_PREFLIGHT_CALIBRATION param 7 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_PREFLIGHT_SET_SENSOR_OFFSETS param 1 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_SET_MESSAGE_INTERVAL param 7 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_REQUEST_MESSAGE param 7 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_DO_TRIGGER_CONTROL param 1 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_DO_TRIGGER_CONTROL param 2 min, max close and increment of 1, should there be a enum?
common.xml: Command MAV_CMD_PAYLOAD_PREPARE_DEPLOY param 1 min, max close and increment of 1, should there be a enum?

# --- Intended orphan enums (referenced by code, not message fields) ---
common.xml: Enum: COMP_METADATA_TYPE is unused
common.xml: Enum: MAV_ARM_AUTH_DENIED_REASON is unused
common.xml: Enum: MAV_FTP_ERR is unused
common.xml: Enum: MAV_FTP_OPCODE is unused
minimal.xml: Enum: MAV_MODE_FLAG_DECODE_POSITION is unused
minimal.xml: Enum: MAV_COMPONENT is unused
standard.xml: Enum: FIRMWARE_VERSION_TYPE is unused
