-
Notifications
You must be signed in to change notification settings - Fork 733
Conversation
shared/domain/src/main/java/com/ivy/domain/usecase/csv/ExportCsvUseCase.kt
Outdated
Show resolved
Hide resolved
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.
Left some comments:
- Export CSV time in UTC
- Use the
TimeConverter
API
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.
Nice! 💯
@akashs056 you neee to fix the |
Or even better and easier, create a |
@ILIYANGERMANOV, I've implemented a |
@akashs056 you have a build error The TestTimeConveter will be red |
I've resolved the initial error with the TestTimeConverter class in my local build. However, now I'm encountering a UncompletedCoroutinesError in the test property - num of row and columns matches the format. It seems to be related to the coroutine not completing within the expected time |
@akashs056 push it so I can have a look - the CI will also provide feedback |
@ILIYANGERMANOV getting the same error again |
shared/domain/src/test/java/com/ivy/domain/usecase/csv/ExportCsvUseCasePropertyTest.kt
Outdated
Show resolved
Hide resolved
@akashs056 fix build errors, update branch and tests should pass on the CI 🤞 I don't see anything incorrect |
@ILIYANGERMANOV Gradle error indicating that the |
It's there, look into StandardTimeConveter. It was merged yesterday - update branch, git pull and open the implementation |
@akashs056 now git pull and implement |
@ILIYANGERMANOV Its ready to merge |
Pull request (PR) checklist
Please check if your pull request fulfills the following requirements:
Screen recording of your changes (if applicable):
What's changed?
Describe with a few bullets what's new:
fixed this issue #3422 previously by #3426
but after the time issue if fixed by #3435 its works incorrectly it exports time at UTC and does not converts it to Local time
So, with this changes its now working perfectly fine exports in users local time and aslo imports in local time zone without any issue
Risk factors
What may go wrong if we merge your PR?
In what cases won't your code work?
Does this PR close any GitHub issues? (do not delete)
Troubleshooting GitHub Actions (CI) failures ❌
Pull request checks failing? Read our CI Troubleshooting guide.