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

Improved: Show Completed Shipments Along with Open Shipments (#380) #381

Merged
merged 8 commits into from
Nov 6, 2024

Conversation

amansinghbais
Copy link
Contributor

Related Issues

#380

Short Description and Why It's Useful

  • Showed completed shipments along with the open shipments.
  • Updated shipment details page for the completed shipments.

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

Before
Screenshot from 2024-08-07 18-07-34

After
Screenshot from 2024-08-07 18-07-13
Screenshot from 2024-08-07 18-07-08

Contribution and Currently Important Rules Acceptance

Copy link
Contributor

@dt2patel dt2patel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please take a look at my comments

@media (min-width: 991px) {
ion-header > div {
display: flex;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@amansinghbais why not use the same pattern as job manager?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dt2patel sir, The same pattern was used in the pipeline page of Job Manager app. Took reference from there only.

@@ -104,7 +122,7 @@ export default defineComponent({
const payload = {
"inputFields": {
"destinationFacilityId": this.user.facilityId,
"statusId": "PURCH_SHIP_SHIPPED",
"statusId": this.selectedSegment === "open" ? "PURCH_SHIP_SHIPPED" : "PURCH_SHIP_RECEIVED",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be available on all pages instead of just the shipments page? I think so right? @amansinghbais

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we can extend this approach to other pages as well to ensure consistency across the application. Initially, the implementation was focused on the shipment page as discussed, but we can apply the same for other pages as well.

@@ -71,20 +71,6 @@ const actions: ActionTree<OrderState, RootState> = {
async getOrderDetail({ commit, state }, { orderId }) {
let resp;

const current = state.current as any
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code is removed to fetch the data every time when we go to detail page, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, so as to avoid old item status issue due to slow Solr updation.

if(!this.isReturnReceivable(current.statusId)) {
showToast(translate("This return has been and cannot be edited.", { status: current?.statusDesc?.toLowerCase() }));
}
console.log(this.current);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this console log intentional?

Copy link
Contributor Author

@amansinghbais amansinghbais Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this is left by mistake, Reverted.

this.lastScannedId = ''
}, 3000)
} else {
showToast(translate("Scanned item is not present within the shipment:", { itemName: this.queryString }));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Searched item...." instead of "Scanned item...."

@ravilodhi ravilodhi merged commit e95c1b3 into hotwax:main Nov 6, 2024
2 checks passed
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.

3 participants