This repository has been archived by the owner on Dec 13, 2020. It is now read-only.
Make sure frontend is connecting to view's websocket endpoint BEFORE view data it's fetched #1820
Comments
|
quick checked locally. works. nothing to test. |
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Jun 11, 2018
[#4191](#4191) Cannot add a product in order [#4169](#4169) Pricing Conditions Jasper [#2539](#2539) Translate report_en_US.properties for order, inout, invoice [#4107](#4107) Customer Revenue Report Excel with Credit Limit [#4149](#4149) User query: IUserQueryRestriction is not built properly all the time [#4168](#4168) Error when posting payment allocation with tax correction and multiple taxes [#4151](#4151) Import: extend process of importing vendors [#4012](#4012) Lot No control in Receipt not working [#4167](#4167) Process C_Flatrate_Term_Extend shall continue if individual terms fail [#1820](metasfresh/metasfresh-webui-frontend-legacy#1820) Make sure frontend is connecting to view's websocket endpoint BEFORE view data it's fetched
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a bug or feature request?
Bug
What is the current behavior?
See metasfresh/metasfresh-webui-api-legacy#977.
Option 2. Frontend fix
Make sure frontend is connecting to view's websocket topic BEFORE the view data is fetched.
e.g. In the case above
What is the expected or desired behavior?
The text was updated successfully, but these errors were encountered: