-
Notifications
You must be signed in to change notification settings - Fork 0
Add post history tracking and restructure timestamps #379
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
Open
mikan3rd
wants to merge
23
commits into
main
Choose a base branch
from
delete_update_at_column
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
6486be7
refactor: remove updated_at field from post schema and related defini…
mikan3rd 5bf2beb
feat: enhance post creation and logging functionality
mikan3rd ca3606d
feat: include post ID in logging during post creation
mikan3rd a9ae53f
feat: add public_id to user creation and tests
mikan3rd 95ee2af
feat: update post schema and tests for user_id handling
mikan3rd 03c240b
fix: remove FIXME comments for public_id generation in user tests and…
mikan3rd 4207aa1
refactor: standardize public_id generation in user and post tests
mikan3rd 55d631a
refactor: update post schema to remove updated_at field and adjust te…
mikan3rd 943db31
refactor: standardize public_id generation in post tests
mikan3rd f6655c1
feat: log post details upon update in post_logs table
mikan3rd 044e5c8
test: integrate post_logs verification in post tests
mikan3rd d7f7d2e
refactor: streamline public_id generation in post creation logic
mikan3rd 2a055a9
feat: add updated_at field to post schema and tests
mikan3rd 4d41a98
feat: add updated_at field to post schema and update required fields
mikan3rd 7370668
fix: include updated_at field in post response object
mikan3rd 6da46b7
fix: update updated_at field in post tests to null
mikan3rd 63e04b6
fix: update updated_at field to allow null values in post schema and …
mikan3rd f65031b
fix: set updated_at field to null in PostCard mock data
mikan3rd b4c2109
feat: introduce first_created_at field in post schema and update rela…
mikan3rd e8bb6cf
refactor: update post schema and mock data to include first_created_a…
mikan3rd 1c7e9bb
refactor: enhance post schema by consolidating properties and improvi…
mikan3rd 0132741
refactor: update post schema and response handling to include updated…
mikan3rd 61afb2e
refactor: streamline post response handling with transformation funct…
mikan3rd File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 file contains hidden or 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 file contains hidden or 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
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: mikan3rd/hono-next-example
Length of output: 3473
🏁 Script executed:
Repository: mikan3rd/hono-next-example
Length of output: 3431
🏁 Script executed:
Repository: mikan3rd/hono-next-example
Length of output: 378
🏁 Script executed:
Repository: mikan3rd/hono-next-example
Length of output: 1160
🏁 Script executed:
Repository: mikan3rd/hono-next-example
Length of output: 3348
🏁 Script executed:
Repository: mikan3rd/hono-next-example
Length of output: 2687
🏁 Script executed:
Repository: mikan3rd/hono-next-example
Length of output: 263
updated_atalways populated; consider nullable to distinguish unedited posts.The API currently always sets
updated_atto a value, making it impossible to signal whether a post has been edited. The database design supports this distinction viafirst_created_at(immutable) vscreated_at(updates on delete&insert pattern), but the API doesn't expose it. If the intent is to indicate "never updated," makeupdated_atnullable in the schema and conditionally null it whenfirst_created_at === created_at. Note: exact timestamp comparison may be unreliable due to microsecond differences; consider row timestamp precision or an explicit edit flag if strict equality checking is needed.🤖 Prompt for AI Agents