You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the field has been changed and it is no longer compatible with 0.6?
It seems that this project would benefit from using modules. Or perhaps a new version of quickfixgo needs producing?
If anyone else runs into this, the easiest solution is:
go get -u github.com/quickfixgo/quickfix@master
Which gets around the fact that go.mod sees version tag v0.6.0 and sycs that, but the other packages are not versioned, so you get the very latest code, which is incompatible with v0.6.0
The text was updated successfully, but these errors were encountered:
Aside- it is usually best to just use the provided generator to generate your own custom messages, fields, and enums. The vanilla generated code is going to give a lot of bloat for most FIX applications.
Looks like this is happening to a few people (glad it's not just me).
I'm still trying to figure things out with this project, and including github.com/quickfixgo/fix42/executionreport is a really nice way to quickly test things out. It would make sense for those projects to have matching tags/modules that pin to quickfixgo, saving a lot of headaches for those of us who are in the early stages, or dabbling about.
This also seems to imply that you should use those, and not necessarily generate your own.
For most FIX applications, these generated resources are sufficient. Custom FIX applications may generate source specific to the FIX spec of that application
Using: go version go1.12.5 darwin/amd64
With modules enabled, go get -u gives:
It seems that the field has been changed and it is no longer compatible with 0.6?
It seems that this project would benefit from using modules. Or perhaps a new version of quickfixgo needs producing?
If anyone else runs into this, the easiest solution is:
Which gets around the fact that go.mod sees version tag v0.6.0 and sycs that, but the other packages are not versioned, so you get the very latest code, which is incompatible with v0.6.0
The text was updated successfully, but these errors were encountered: