Fix #57: User.Name not being populated on timeentry list #58
Conversation
This file contains 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
The `Name` field of the `User` object may sometimes be used by Harvest to populate the full name. The `User` structure needs to be aware of this and optionally populate this on a JSON decode if the `User` field is present.
stgraham2000
force-pushed
the
ioka-technologies/fix-user-not-being-populated
branch
from
192c6de
to
b0dde42
Compare
|
Thanks @stgraham2000 for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
Namefield of theUserobject may sometimes be used by Harvest to populate the full name. TheUserstructure needs to be aware of this and optionally populate this on a JSON decode if theUserfield is present.