Skip to content
This repository has been archived by the owner on Dec 13, 2020. It is now read-only.

grid view websocket events for underlying view are not handled #387

Closed
teosarca opened this issue Feb 21, 2017 · 2 comments
Closed

grid view websocket events for underlying view are not handled #387

teosarca opened this issue Feb 21, 2017 · 2 comments
Assignees
Milestone

Comments

@teosarca
Copy link
Member

Test case:

  • open receipt candidates
  • select a line and receive some HU(s)
  • create material receipt from one of them

At this moment, the backend is firing an websocket event like following:
topic: /view/a429a03c-9d74-4e92-9c03-609a5625fc78
event: {viewId=a429a03c-9d74-4e92-9c03-609a5625fc78, windowId=540196, fullyChanged=true, changedIds=[1000001]}

Because the underlying receipt candidate is was changed (i.e. QtyMoved increased, QtyToMove decreased).
But it seems that the frontend is no longer listening to that topic.

image

@teosarca
Copy link
Member Author

note: my colleagues told me that sometimes works sometimes not.
in meantime i am checking the backend side too.

@damianprzygodzki
Copy link
Contributor

damianprzygodzki commented Feb 23, 2017

I've played with that a bit. It is not reproducable.

Always when the event is coming and has fullyChanged property set the app is getting documentView with its ID.

Furthermore, the documentView is always listening WS until it is unmounted (it means that component is destroyed).

Checked by quickActions and actions in nav menu. After both WS about change in documentViews, the refresh calls are triggered for both viewIds.

screen shot 2017-02-23 at 10 20 42

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants