mirror of
				https://github.com/superseriousbusiness/gotosocial.git
				synced 2025-11-03 17:52:24 -06:00 
			
		
		
		
	* Add Swagger spec test script * Fix Swagger spec errors not related to statuses with polls * Add API tests that post a status with a poll * Fix creating a status with a poll from form params * Fix Swagger spec errors related to statuses with polls (this is the last error) * Fix Swagger spec warnings not related to unused definitions * Suppress a duplicate list update params definition that was somehow causing wrong param names * Add Swagger test to CI - updates Drone config - vendorizes go-swagger - fixes a file extension issue that caused the test script to generate JSON instead of YAML with the vendorized version * Put `Sample: ` on its own line everywhere * Remove unused id param from emojiCategoriesGet * Add 5 more pairs of profile fields to account update API Swagger * Remove Swagger prefix from dummy fields It makes the generated code look weird * Manually annotate params for statusCreate operation * Fix all remaining Swagger spec warnings - Change some models into operation parameters - Ignore models that already correspond to manually documented operation parameters but can't be trivially changed (those with file fields) * Documented that creating a status with scheduled_at isn't implemented yet * sign drone.yml * Fix filter API Swagger errors * fixup! Fix filter API Swagger errors --------- Co-authored-by: tobi <tobi.smethurst@protonmail.com>
		
			
				
	
	
		
			22 lines
		
	
	
	
		
			515 B
		
	
	
	
		
			Go
		
	
	
	
	
	
			
		
		
	
	
			22 lines
		
	
	
	
		
			515 B
		
	
	
	
		
			Go
		
	
	
	
	
	
// +build gofuzz
 | 
						|
 | 
						|
package semver
 | 
						|
 | 
						|
func Fuzz(data []byte) int {
 | 
						|
	d := string(data)
 | 
						|
 | 
						|
	// Test NewVersion
 | 
						|
	_, _ = NewVersion(d)
 | 
						|
 | 
						|
	// Test StrictNewVersion
 | 
						|
	_, _ = StrictNewVersion(d)
 | 
						|
 | 
						|
	// Test NewConstraint
 | 
						|
	_, _ = NewConstraint(d)
 | 
						|
 | 
						|
	// The return value should be 0 normally, 1 if the priority in future tests
 | 
						|
	// should be increased, and -1 if future tests should skip passing in that
 | 
						|
	// data. We do not have a reason to change priority so 0 is always returned.
 | 
						|
	// There are example tests that do this.
 | 
						|
	return 0
 | 
						|
}
 |