-
Notifications
You must be signed in to change notification settings - Fork 2
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: add/use RFC3339 fields in requests #233
base: master
Are you sure you want to change the base?
Conversation
@Value | ||
@Builder | ||
public class PostFeedbackRequestBody { | ||
FeedbackEvent event; | ||
Long timestamp; | ||
Instant occurredAt; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change once PostFeedbackRequestBody
is public
, but I'm considering it as not because the user isn't supposed to use this class directly. Should change the visiblity of these internal classes to avoid issues?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll change it in another PR to be released together with the breaking changes.
8401bc0
to
33c576a
Compare
@Deprecated Long timestamp; | ||
Instant collectedAt; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I decided to mark the old field as deprecated and add the new here as this class is used by the user. Given that we are bumping the major due to the removal of GetSignup
, should we take the opportunity and remove the old field too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll remove it later together with the other breaking changes.
7b4e6d8
to
43ff19b
Compare
Timestamp fields that store time as milliseconds since epoch are being replaced by fields that store it as a RFC 3339 string. This commit: - Removes POST /feedbacks `timestamp` field, replacing it with `occurred_at`. Removal is possible because this field is not in the public API. - Add `collected_at` to POST /signups' `additional_locations`. This field should be used instead of the existing `timestamp`.
43ff19b
to
3285df2
Compare
Proposed changes
Timestamp fields that store time as milliseconds since epoch are being replaced by fields that store it as a RFC 3339 string.
This commit:
timestamp
field, replacing it withoccurred_at
. Removal is possible because this field is not in the public API.collected_at
to POST /signups'additional_locations
. This field should be used instead of the existingtimestamp
.Checklist