fix: populate the User from UserID when get application and job #4178
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.
This pull request introduces changes to the
Application
andJob
models in themanager/models
package to improve how relatedUser
data is handled. The most significant updates include marking theUser
field withgorm:"-"
to exclude it from ORM operations and addingAfterFind
hooks to populate theUser
field after database queries.Changes to
Application
model:User
field withgorm:"-"
to exclude it from ORM operations. (manager/models/application.go
, manager/models/application.goR19-R42)AfterFind
hook to populate theUser
field after database queries by fetching the associatedUser
based onUserID
. (manager/models/application.go
, manager/models/application.goR19-R42)Changes to
Job
model:User
field withgorm:"-"
to exclude it from ORM operations. (manager/models/job.go
, manager/models/job.goL28-R47)AfterFind
hook to populate theUser
field after database queries by fetching the associatedUser
based onUserID
. (manager/models/job.go
, manager/models/job.goL28-R47)Description
Related Issue
Closes #4171
Motivation and Context
Screenshots (if appropriate)
Types of changes
Checklist