-
Notifications
You must be signed in to change notification settings - Fork 12
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
EPL-1196: AverageAlgorithm class can be improved by showing the product.getName() on the OBException #281
Labels
bug
Something isn't working
Comments
brunoromerosmf
changed the title
EPL-1196: AverageAlgorithm class can be improved by showing the product.getSearchKey() on the OBException
EPL-1196: AverageAlgorithm class can be improved by showing the product.getName() on the OBException
Jan 22, 2024
tomirodeghiero
added a commit
that referenced
this issue
Jan 22, 2024
EPL-1196: Include product.getName() in OBException
tomirodeghiero
pushed a commit
that referenced
this issue
Jan 22, 2024
EPL-1196: Include product.getName() in OBException
tomirodeghiero
added a commit
that referenced
this issue
Jan 22, 2024
EPL-1196: Include product.getName() in OBException
tomirodeghiero
added a commit
that referenced
this issue
Jan 23, 2024
EPL-1196: Directly embed product name and search key in OBException message to align with CostingUtils.java formatting
tomirodeghiero
added a commit
that referenced
this issue
Jan 23, 2024
tomirodeghiero
added a commit
that referenced
this issue
Jan 23, 2024
Issue #281: AverageAlgorithm class can be improved by showing the product.getName() on the OBException
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Error's description
The OBException of getOutgoingTransactionCost() method of AverageAlgorithm class can be improved by showing the product.getName().
In case of variants or generic products is difficult to tell which product is throwing the exception in case of errors.
Steps to reproduce the error
Affected version
23.4.0
Solution Design (optional)
Please find attached how Openbravo has solved this problem.
https://issues.openbravo.com/view.php?id=39863
The text was updated successfully, but these errors were encountered: