Fix: Fixed getArgType reflection value logic #276
Merged
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.
What this PR does:
Fixed getArgType reflection value logic.
Source
![1630564699562_2A57E06F-1539-4bec-9869-C7369CF69DCA](https://user-images.githubusercontent.com/9605663/131800743-e375621c-1935-44ee-8273-e3d98fde2c89.png)
Demo
![1630564706769_6D073A5C-CF4C-43f4-BB6B-DDF36991CC4B](https://user-images.githubusercontent.com/9605663/131800815-71b34990-6405-4d97-bae5-dda8e803dae9.png)
Print
![1630564711927_CBBCA459-7108-4afc-888F-A86FA1F971BC](https://user-images.githubusercontent.com/9605663/131800878-3ee6dbe9-7b74-4f8c-9c8a-8b9acde00768.png)
Analyse
发现原版指向的类型是struct,如果使用t.Elem()会指向slice
测试了map,结果也是相似的
Conclusion
当getArgType的switch跑到default,且入参为指针时,很可能都会当成一般struct去处理
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: