dhextras / freight-pallet-calc Goto Github PK

Issue Description:

Currently, the application only accepts integer values for product dimensions (width, depth, height). However, in real-world scenarios, product dimensions can often be in decimal points (e.g., 12.5cm). This limitation can impact the accuracy of the palletization calculation.

Proposed Solution:

Modify the application to accept decimal values for product dimensions. Update the input validation logic and ensure that the calculations can handle decimal points for width, depth, and height. Additionally, adjust the UI to provide a better user experience when entering decimal values.

Steps to Reproduce:

1. Open the application.
2. Enter a product with decimal values for width, depth, or height (e.g., 12.5cm).
3. Attempt to calculate pallet size. and ensure everything works

Expected Behavior:

The application should accept and correctly process decimal values for product dimensions without any errors. Ensure that the palletization algorithm handles decimal points appropriately.

Additional Information:

• Update relevant input validation functions.
• Adjust the user interface to handle decimal input for product dimensions.
• Test the application with various product dimensions, including both integer and decimal values.

Note:
Make sure to update the code and user interface to handle decimal values appropriately, ensuring accurate palletization calculations.

FeatureDescription

Updating color theme, removing minimum depth constraint, and styling the pallet for better integration with the main site.

Expected Behavior

The color theme of the application should match the main site's red and black scheme. The minimum depth constraint for the pallet should be removed and set to a default value of 110. Additionally, the pallet styling should be adjusted for better integration.

Definition of Done / Testing

• Verify that the color theme matches the main site's red and black scheme.
• Confirm that the minimum depth constraint for the pallet is removed and set to a default value of 110.
• Test and ensure that the pallet styling aligns with the desired integration.

Additional Information

The updates are intended to enhance the visual integration of the application with the main site.

• Note: Half of the issue has been solved already by pullreq #7

Motivation

The current codebase lacks modularity and could benefit from a more organized structure. By modularizing the code using a bundler like Webpack or Vite, we aim to improve maintainability, reusability, and overall code structure.

Implementation

Integrate Webpack/Vite to create a modular system for the existing codebase. This involves breaking down the code into manageable modules and using the bundler to handle dependencies efficiently.

Testing

• Verify that the application functionalities remain unaffected after the modularization.
• Check if the build process is successful using Webpack/Vite.
• Ensure that the final bundle size is reasonable and optimized.
• Make sure even after modularizing nothing changed on the user expirience nor on app logic

Screenshots

Attach screenshots showing the modularized code structure and any relevant terminal outputs during the build process.

Checklist

• Build process is optimized.
• Webpack/Vite integrated successfully.
• Application functionalities remain intact.
• Code is organized into modules.

Motivation

Security is paramount. The current codebase may be susceptible to security vulnerabilities, such as the use of innerHTML. This issue aims to identify and fix security vulnerabilities in the code.

Implementation

• Identify potential security vulnerabilities, especially related to innerHTML usage.
• Implement security best practices, such as using DOM purifiers or alternative methods to mitigate security risks.

Testing

• Perform security testing to ensure vulnerabilities are addressed.
• Verify that the application remains functional and secure after implementing fixes.

Screenshots

Attach relevant screenshots or code snippets showing the areas where security fixes were applied.

Checklist

• Security vulnerabilities identified.
• Security fixes implemented successfully.
• Application remains secure and functional after fixes.