Repository navigation
Reject empty files and name the purpose param - #856
Merged
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Official API alignment (FS-17, FS-18).
POST /v1/fileswith an empty file returns 400File is empty.(null code and param) and stores nothing.purposepart returnsMissing required parameter: 'purpose'.and any other valueOnly purpose user_data is supported., both withparam: "purpose"and the Files routes' null code.source-files.md+ zh) and the Web Files copy updated.Checks:
go test ./internal/files ./internal/api -run 'SourceFile|Files|TestCreate',go vet ./..., gofmt.Need help on this PR? Tag
@codesmith-botwith what you need.