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

Standardize the way validity dates are sent out from the services #4

Open
camba1 opened this issue Jan 25, 2021 · 0 comments
Open

Standardize the way validity dates are sent out from the services #4

camba1 opened this issue Jan 25, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@camba1
Copy link
Owner

camba1 commented Jan 25, 2021

Currently, depending on wether the DB is SQL or No SQL, the validity dates and the modification fields are been sent out to the client either inline or as part of an object within the dataset. This is due to how the fields are mapped in the porto definition.
When creating the services we switched midway the way we handled those fields in the porto definitions to use imported global definitions but never went back to change it in the promotion and customer services.
Bottom line, all services should handle those fields the same way It is done in the product and customer services, independent of how they are stored in the DB

@camba1 camba1 added the enhancement New feature or request label Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant