Dev #248
Merged
Dev #248
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
Changed the splashscreen version in pubspec.yaml from 1.2.0 to flutter_native_splash: 1.3.3. Updated also the distributionUrl in gradle-wrapper.properties file from version 7.0.2-all to 7.4.2-bin. #225
…change-address-ui
Implemented UI for changing address #14
…Delete-user-account-UI
Improved the spacing between "Change password" and "Update" buttons. It's now based on the device's hight to prevent scrolling.
…ign-docs Added new design docs #223
…ne-docs Upload new site and timline docs from Bruce
…t Planning & Retrospective.md
…t-UI Feature/#18 delete user account UI
…ing-notes Update and rename Notes - Sprint Planning Meeting.md to Notes - Sprin…
…laced style elements in the code where the new class could be utilized.
…n-the-FlexiChargeTheme-class Put font styles in the FlexiChargeTheme class
Implemented the UI for changing password.
…ing-sprint-docs Update Notes - Sprint Planning & Retrospective.md
Updated project dependencies and added the Mockito package. Fixed the code that was deprecated in QR Scanner view and viewmodel. Updated Kotlin version.
Added another text field so that the user does not accidentally enter the wrong new password.
…Password-text-field Added "Repeat Password" text field
The email entered follows to the next screen and is automatically set as a default value for the email text field.
I interpreted the task incorrectly and it's now fixed. Also another feature was added, being able to use the defaultInput parameter in the UserFormInput class.
…-field-when-verifying-email Feature/#244 delete email text field when verifying email
It no longer starts charging when it shouldn't. After the bottom sheet was closed it always started "charging" no matter what. Now it only starts when you click the button.
The code now checks if the selected charger is "Available" or not. If the charger is available it will start the charging process. Otherwise it wont do anything.
Centered the headers
…scanned-charger-does-not-exist Fixed charging starting when it shouldn't
…rging Test/#259 investigate test charging
…ved-button You can no longer start charging if the charger is not available
Fixed the "Stop Charging" and "Push Down" buttons not appearing on the top sheet when it starts charging.
The loading bar previously went rtl but now it goes ltr like it should.
Previously, the user location was hardcoded to "Barnarpsgatan 68". Now, it uses the GeoCoding package from Flutter to convert the user's coordinates to an address that displays in the bottom sheet when selecting a charger.
The charging summary now displays the time that the charging stopped at.
The app is now getting live metics data from the backend and displays it in the top sheet when the charging process begins and ends.
…reen-loads-right-to-left Loading bar now goes ltr
…nt-planning Update Notes - Sprint Planning & Retrospective.md
…-metrics-from-backend Feature/#53 show live charging metrics from backend
The boxes are now back and are showing as they did before
Update pubspec.yaml
…he-charger-id's-dissapeared Fixed white boxes that had dissapeared
The documentation can be found in the documentation files in the documentation folder under the Notes & Requirements part.
This commit adapted the charger components to align with recent changes in the backend, ensuring compatibility and functionality between the front-end and back-end systems.
Changed Transaction class name to OldTransaction to make it obvious that the Transaction object is outdated and should be replaced with the new one.
…tation-about-how-to-run-the-project-for-the-first-time Added documentation on how to start the app
…kend-incoming-changes Feature/#288 adapt code to backend incoming changes
…kend-incoming-changes Implemented new transaction functionality
ellencarlsson
approved these changes
Oct 12, 2023
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.
No description provided.