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

Move the job grid into its own class #1283

Merged
merged 2 commits into from
Apr 13, 2020
Merged

Conversation

jpwhite4
Copy link
Member

@jpwhite4 jpwhite4 commented Apr 10, 2020

This job grid is to be used by the job efficiency component as well as the
JobComponent so it makes sense to move the code into its own class.

This change does not alter the behaviour of the JobComponent but there are a couple of changes:

  1. The refresh function is now triggered by an event.
  2. The jobgrid has the capability of doing drilldown for a different realm than the original query realm.

This job grid is to be used by the job efficiency component as well as the
JobComponent so it makes sense to move the code into its own class.
This change does not alter the behaviour of the JobComponent.
The moment library is packed with xdmod, but the linter rules omitted
this information.
@jpwhite4 jpwhite4 added this to the 9.0.0 milestone Apr 10, 2020
@jpwhite4 jpwhite4 added the Category:User Dashboard Screen shown after user login label Apr 10, 2020
@jpwhite4 jpwhite4 merged commit 7e938ca into ubccr:xdmod9.0 Apr 13, 2020
@jpwhite4 jpwhite4 deleted the jobgrid branch April 13, 2020 15:18
@jtpalmer jtpalmer added the enhancement Enhancement of the functionality of an existing feature label Aug 10, 2020
@jtpalmer jtpalmer changed the title Move the job grid into its own class. Move the job grid into its own class Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:User Dashboard Screen shown after user login enhancement Enhancement of the functionality of an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants