-
Notifications
You must be signed in to change notification settings - Fork 20
Provide user ids in team + time entries #146
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
mlahp7
wants to merge
21
commits into
AutoIDM:main
Choose a base branch
from
mlahp7:provide-user-ids-in-team
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
21 commits
Select commit
Hold shift + click to select a range
b785339
WIP, pass down user_ids to the children of Team
mlahp7 de82323
Remove if for now
mlahp7 d39ad16
Fix time entry schema
mlahp7 e59ec0f
Another schema fix
mlahp7 437335e
Formatting
mlahp7 5661eab
Super weird, but when we don't have access to the task related to the…
mlahp7 0e39e9c
task custom type can be a number
mlahp7 ae8d960
list ids are nullable
mlahp7 b208d68
Folder id nullable
mlahp7 c0d3783
Another null field. It seems this may be a bug with the clickup api. …
mlahp7 cd3a7fe
Pass assignees via setting / conf
mlahp7 bef9070
Allow for time_entry start date to know when to start fetching time e…
mlahp7 efdf2fe
Add new conf to meltano.yml
mlahp7 e18b632
Fix conversion issue
mlahp7 f1ab1ce
Bad import
mlahp7 061b55c
Take 59 with format
mlahp7 9aa2d07
Attempt to use 'at' field from time entry as replication key
mlahp7 581e52b
Merge branch 'AutoIDM:main' into provide-user-ids-in-team
mcarriere cc47a89
Feedback tweaks (#1)
mlahp7 527af20
Update current status of Time Entries data in the readme
mlahp7 372c098
Merge branch 'main' into provide-user-ids-in-team
mlahp7 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
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
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.
Just noticed this, we should really be using the
atreplication key here not just the start_date.See https://sdk.meltano.com/en/latest/incremental_replication.html#incremental-replication , specefically
self.get_starting_timestamp(context), and instead of having a seperate start date fortime_entrywe should probably just drop thetime_entry_start_dateconfiguration and just document thatstart_datedoes whattime_entry_start_dateis currently documented to doThere 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've added an if statement to fallback to the time_entry_start_date in the case that the state is empty on a user's first execution. Otherwise it would use the "at" field as the replication key as suggested.
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.
why not use
self.get_starting_timestamp(context)here? the start_date config variable is already use in this function so we don't needtime_entry_start_dateeither, unless you think we need two seperate start date windows?