解决使用异常，类找不到，开发不便利的问题 #90
Open
Conversation
This file contains 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
从laravel拓展的开发角度看，采用config.php，命名，即没有体现出oss拓展包的含义，又占用了一个config通用关键词，非常容易引起误解
Log引入路径错误，然后获取文件那里异常直接抛出，非常不利于开发，这并不是一个致命的错误， 实际开发场景中，经常会去读一个不存在的文件，比如：系统配置里面，做系统迁移，数据库记录文件的数据并不存在， 前提是得保证系统运行下去，而不是因为一个非系统耦合的文件找不到导致整个系统奔溃， 如果非要这么做的话，把config(‘oss.debug’)引入进来也是可以了， 为了简便开发，这里记录一个警告日志足够了！
删除资源是正常操作，但如果能明确资源并不存在，那么直接返回不存在，删除操作就不执行，这样才比较合理， 文件本来就不存在，直接抛出异常，程序又奔溃了
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.
解决使用异常，类找不到，开发不便利的问题