Support for calculation of prices accompanying the price for sale #600
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.
…gured Currently server generates or requires access to the certificates even if there is no TLS configured on any endpoint. Also we shouldn't generate and provide client certificates if MTLs is not configured. Also this patch changes how gRPC readiness probe works. Now Managed channel is used.
…on-when-no-tls-endpoint-is-configured fix(#588): Avoid certificate generation when no TLS endpoint is confi…
…gured Currently server generates or requires access to the certificates even if there is no TLS configured on any endpoint. Also we shouldn't generate and provide client certificates if MTLs is not configured. Also this patch changes how gRPC readiness probe works. Now Managed channel is used.
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
Added info message after evita server start including exception stacktrace.
Added info message after evita server start including exception stacktrace.
Added info message after evita server start including exception stacktrace.
…eference-price' into 549-calculation-of-appropriate-reference-price
…after-compaction # Conflicts: # evita_store/evita_store_server/src/main/java/io/evitadb/store/catalog/DefaultCatalogPersistenceService.java
…ken-after-compaction fix(#590): Catalog data file gets broken after compaction
…urns-no-result' into dev
…-reference-price feat(#549): calculation of appropriate reference price
…d-for-hierarchically-fetched-parents' into dev
…nt-groups-enables-hassense-for-invalid-facets' into dev
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.