-
Notifications
You must be signed in to change notification settings - Fork 10
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
Feature/170 сonfigured app distribution #174
The head ref may contain hidden characters: "feature/170-\u0421onfigured-AppDistribution"
Conversation
Made: 1. api 2. response 3. dto 4. DataMapper 5. Exception mapper
Made: 1. di 2. Repository 3. Interactor 4. DomainMapper 5. Data 6. State 7.ExceptionToErrorMapper
Made: 1. PasswordRecoveryViewModel 2. State
…m/CashAdv/CashADV into 71-Password-Recovery
Made:
1. Solved the "empty message exception" 2. Renamed the class names to more understandable ones
1. Resolved conflicts
1. Made the lines shorter
1) removed context from viewmodel 2) added Resources in viewmodel 3) renamed fun setEmail(email:String) on requestRecovery() 4) removed isResetPasswordInProgress() 5)I removed the extra one logDebugMessage 6)formatted the code 7) removed DTO from Domain 8) the code field is cleared when an error occurs
1) Called onBackPressedDispatcher.addCallback in viewmodel 2) added a theme
1) made the creation of a unique version number 2) added notification to testers about new builds
1) I did that triggers the workflow not only for dev branch 2) Did that buildNumber = GITHUB_SHA::7
@@ -0,0 +1,128 @@ | |||
package app.cashadvisor.authorization.data |
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.
это из другого пулл-реквеста, надо убрать
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.
удалить эти файлы и сделать новый push ?
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.
лучше сделать чистую ветку от dev и там модифицировать только то, что нужно для задачи
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.
сделай чистый PR и тогда можно будет нормально смотреть что ты сделал
pull_request: | ||
types: | ||
- closed | ||
branches: [ "dev" ] | ||
|
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.
а почему убрать проверку на dev-бранч?
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.
я так понял уведомления будут отправляется если только сделать мердж ветки dev в main, но нам же для всех веток надо? Поэтому решил убрать dev.
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.
это условие будет срабатывать при закрытии PR в ветку dev
то есть когда мы мерджим PR в dev, тут всё правильно
No description provided.