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.
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
Update goal in segment #5027
base: master
Are you sure you want to change the base?
Update goal in segment #5027
Changes from 4 commits
c99d812
47988c0
fa7bff4
5a484d7
5fbe145
f549882
7c5a436
4aa0560
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 requires inline commentary so the reader won't have to wonder what are we trying to achieve here
Check failure on line 111 in test/plausible/goals_test.exs
GitHub Actions / Build and test (ce_test, postgres:16)
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.
issue: Noticed that we also override segment
updated_at
.If that's intentional, it would be good to assert it here as well, with something like
segment.updated_at < updated_segment.updated_at
.Alternatively, we may want to not override updated_at on these automatic updates. May be confusing when the message in the UI (
Last updated at <stamp> by <name>
) doesn't match with their usual online time.Or we could also just rephrase it in the UI:
Last updated at <stamp>, belongs to <name>
or similar.