Fix incorrect deprecation warnings on defaults (#348)
This change ensures that deprecation warnings are only raised when either a deprecated field is explicitly set or a deprecated message is initialised. Resolves: #347
This commit is contained in:
		
				
					committed by
					
						 GitHub
						GitHub
					
				
			
			
				
	
			
			
			
						parent
						
							9c1bf25304
						
					
				
				
					commit
					69f4192341
				
			| @@ -4,8 +4,11 @@ package deprecated; | ||||
|  | ||||
| // Some documentation about the Test message. | ||||
| message Test { | ||||
|     // Some documentation about the value. | ||||
|     option deprecated = true; | ||||
|     int32 v = 1 [deprecated=true]; | ||||
|     Message message = 1 [deprecated=true]; | ||||
|     int32 value = 2; | ||||
| } | ||||
|  | ||||
| message Message { | ||||
|     option deprecated = true; | ||||
|     string value = 1; | ||||
| } | ||||
|   | ||||
		Reference in New Issue
	
	Block a user