Closed reatang closed 5 months ago
So what you have done is encapsulating releated methods in the header
object?
please make the ci pass
So what you have done is encapsulating releated methods in the
header
object?
Yes, make the Header function cohesive.
In fact, from a programming perspective, it should not be designed in this way, which couples the presentation layer and the application layer. An encoding layer for fbs
and golang
objects should be provided.
Now what I do is explicitly layer it in a class.
其实从程序设计角度来说,不应该如此设计,这让表现层和应用层耦合了。应该提供一层 fbs 和 golang 对象的转换层。现在我做的就是在一个类型中显式的分层。
Attention: 1 lines
in your changes are missing coverage. Please review.
Comparison is base (
a265bcd
) 79.62% compared to head (5b5d631
) 79.78%.:exclamation: Current head 5b5d631 differs from pull request most recent head 8a00498. Consider uploading reports for the commit 8a00498 to get more accurate results
Files | Patch % | Lines |
---|---|---|
internal/http/header.go | 97.82% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
please make the ci pass
Header should manage its own changes and builds