Skip to content
New issue

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

UI: Live updating views #3936

merged 48 commits into from Mar 8, 2018

UI: Live updating views #3936

merged 48 commits into from Mar 8, 2018


Copy link

@DingoEatingFuzz DingoEatingFuzz commented Mar 5, 2018

Utilize blocking queries to update all views in the UI as the cluster state changes.


  • Improved acceptance testing for polling

Now that blocking queries are going to be in play, We can no longer
pretend the two requests are one, since they have independent nomad
- Service to manage X-Nomad-Index values
- Adapter method for reloading relationships with additional params
- Pattern for watching models and model relationships using EC
- Key data using datum label
  (when something goes from number, to zero, to number again)
- Retain active and inactive classes across data updates
Ember Data doesn't do this by default, instead opting to be as
non-destructive as possible. However, this is desired behavior.
When the findAll response from the server no longer has them.
UI: Background Polling Step 1 - Foundational support & jobs
They are only for the overview page, not the whole hierarchy
It's only necessary for the list view, not the entire route hierarchy
It doesn't need to impact the entire route hierarchy
deactivate happens _after_ the new route's model hook, which
results in the possibility of canceling new requests right
after they are made rather than existing open connections
@DingoEatingFuzz DingoEatingFuzz merged commit 220790f into master Mar 8, 2018
3 checks passed
@DingoEatingFuzz DingoEatingFuzz deleted the f-ui-polling branch Mar 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

Successfully merging this pull request may close these issues.

None yet

1 participant