-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat(#549): calculation of appropriate reference price #595
Merged
lukashornych
merged 13 commits into
dev
from
549-calculation-of-appropriate-reference-price
Jun 3, 2024
Merged
feat(#549): calculation of appropriate reference price #595
lukashornych
merged 13 commits into
dev
from
549-calculation-of-appropriate-reference-price
Jun 3, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds ability to calculate multiple prices respecting the price inner record handling logic and selected price for sale for visualization purposes.
Reimplemented logic for calculation all prices for sale function to mimic the logic in price for sale function (the original logic was flawed). Added new method for calculating all prices for sale with accompanying prices.
…eference-price' into 549-calculation-of-appropriate-reference-price # Conflicts: # evita_external_api/evita_external_api_graphql/src/main/java/io/evitadb/externalApi/graphql/api/catalog/dataApi/resolver/constraint/EntityFetchRequireResolver.java # evita_external_api/evita_external_api_graphql/src/main/java/io/evitadb/externalApi/graphql/api/tracing/OperationTracingInstrumentation.java
…eference-price' into 549-calculation-of-appropriate-reference-price
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.