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: barcode identifier selector and scanning based on selected identifier (#845) #846

Closed
wants to merge 4 commits into from

Conversation

amansinghbais
Copy link
Contributor

@amansinghbais amansinghbais commented Nov 6, 2024

Related Issues

#845

Short Description and Why It's Useful

Added support for the barcode identification scanning.

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

Screenshot from 2024-11-06 12-33-20

Contribution and Currently Important Rules Acceptance

@@ -286,7 +289,8 @@ export default defineComponent({
orderLimitType: 'unlimited',
fulfillmentOrderLimit: "" as number | string,
facilityGroupDetails: {} as any,
isEComInvEnabled: false
isEComInvEnabled: false,
barcodeContentMessage: translate("Only allow received quantity to be incremented by scanning the barcode of products. If the identifier is not found, the scan will default to using the internal name.", { space: '<br /><br />' })
Copy link
Contributor

Choose a reason for hiding this comment

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

"Only allow received quantity......" should be changed to "Only allow shipped quantity"

}
},

async cretaBarcodeIdentificationPref({ commit }) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Correct typo.

@@ -13,4 +13,5 @@ export default interface UtilState {
facilities: any;
shipmentGatewayConfigs: any;
isForceScanEnabled: boolean;
barcodeIdentificationPref: any;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
barcodeIdentificationPref: any;
barcodeIdentificationPref: string;

}

// not checking for resp success and fail case as every time we need to update the state with the
// default value when creating a scan setting
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
// default value when creating a scan setting
// default value when creating a store setting


async updateForceScanStatus({ commit }, payload) {
commit(types.UTIL_FORCE_SCAN_STATUS_UPDATED, payload)
},

async updateBarcodeIdentificationPref({ commit }, payload) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This action is not used anywhere, we should use this method wherever we are updating the state for barcode identifier, also we need to clear the barcode identifier value of logout.

@@ -21,7 +21,8 @@ const utilModule: Module<UtilState, RootState> = {
productStores: [],
facilities: [],
shipmentGatewayConfigs: [],
isForceScanEnabled: false
isForceScanEnabled: false,
barcodeIdentificationPref: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

As we have defined internalName as default value for barcodeIdentifier we can have the same value here in state as its default declaration

@amansinghbais
Copy link
Contributor Author

amansinghbais commented Nov 12, 2024

Closing this PR since latest commit got stuck in github glitch, Processing updates

Created new PR for this: #851

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