We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I was wondering why the network header types are exported along with the creation of them?
Here the type is exported type Binary2Bytes struct {
And then the instantiation of it is also exported? func NewBinary2BytesHeader() *Binary2Bytes {
Any reason to have the type exported? When would I use one over the other? Does this need to be documented?
The text was updated successfully, but these errors were encountered:
Should we move the headers to https://github.com/moov-io/iso8583-connection as it seems a more relevant place for them?
I also think we don't need a constructor here, but we also should not export Len -> len as well.
Len
len
Sorry, something went wrong.
No branches or pull requests
I was wondering why the network header types are exported along with the creation of them?
Here the type is exported
type Binary2Bytes struct {
And then the instantiation of it is also exported?
func NewBinary2BytesHeader() *Binary2Bytes {
Any reason to have the type exported? When would I use one over the other? Does this need to be documented?
The text was updated successfully, but these errors were encountered: