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

Implemented: Functionality to fetch more jobs on all pages(#2vjxdha) #274

Merged
merged 48 commits into from
Nov 18, 2022

Conversation

shashwatbangar
Copy link
Contributor

@shashwatbangar shashwatbangar commented Nov 8, 2022

Related Issues

Closes #257

Short Description and Why It's Useful

Now we have moreJobs section in our pages (Inventory, PreOrder, Order, Product), so if there are more jobs for the specific page, we can view in this section.

Screenshots of Visual Changes before/after (If There Are Any)

Screen.Recording.2022-10-18.at.5.22.10.PM.mov

IMPORTANT NOTICE - Remember to add changelog entry

Contribution and Currently Important Rules Acceptance

Earlier we had MoreJobs component lying in Inventory view, now it is a seperate component that can be used anywhere(#2vjxdha)
…jxdha)

Earlier, we had MoreJobs sections in Inventory page, now defined seperately a MoreJobs component with its seperate states, mutations, actions so it can be used anywhere in the app, just need to change enumTypeId for the page we are fetching MoreJobs(#2vjxdha)
…right side(#2vjxdha)

Currently in process of fixing this bug, jobConfiguration component opens up below instead of right side. Using emitter to emit the job from MoreJobs component to the component it is placed in & when we click on the job in MoreJobs component, it send the job details through emitter so respective component recieves the job details and that component jobConfiguration will open up the configuration in right side. However it doesn't seems to work.
Earlier JobConfiguration component was opening up below the list of MoreJobs & we expect it open on right side of jobs, Now it is working fine
Earlier we were fetch MoreJobs for all the pages with same enumTypeId, now jobs will be fetched according to the page we are on i.e if on Inventory, More Jobs for inventory page will be fetched, also removed unused code, fetched MoreJobs when component gets mounted instead of created & used unique key to display MoreJobs
Now we are fetching MoreJobs acoording to the page we are coming from like Inventory or Product, improved variable namings and removed unused code
…dha)

Earlier we had only one state for more jobs and we were storing all moreJobs in it, now we have seperate job states for pending and draft jobs, also if no jobs present, component will be hidden. If no morePending jobs present then we will show draft ones
Now job title will get set using getEnumName getter which takes systemJobEnumId and return corresponding name associate with that enum
…#2vjxdha)

Suppose a job is draft & pending, so now we are fetching all moreJobs jobs & if any job is pending and draft, we will show its pending job
… moreJobs getter. Removed same payload being passed from Inventory, PreOrder, Order & Product pages and centralized it in moreJobs action(#2vjxdha)
…obName present, it was throwing error(#2vjxdha)
… payload while fetching pendingJobs(#2vjxdha)
shashwatbangar and others added 16 commits November 3, 2022 19:05
…eId to get temporalExpression, now corrected and passing tempExprId in getter to fetch correct temporalExpression(#2vjxdha)
…ingle job status at a time, also we were setting title data property in job title through, now removed title & directly updating jobTitle through getEnumName getter(#2vjxdha)
…urning off due to pass by reference problem, now working fine(#2vjxdha-n)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement more jobs section on all pages
2 participants