This repository has been archived by the owner on Mar 24, 2024. It is now read-only.
[Back | Front] Split Name - [Front] Order Confirm #114
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
Updated import statement in Confirm.tsx to include additional components from "@fluentui/react-icons/lib/fonts" and replaced ColFlex with Flex. Updated version of Confirm component in author comments. Added new 'title' style property to useStyles hook. Replaced Toast component with DialogSurface component for displaying success message after order placement. Swapped order of Update([]) and Nav("History", data) functions in onSuccess function and added new onStatusChange function to toast dispatch function.
This commit splits the `Name` field into two separate fields: `Surname` and `Forename` across various classes and components including `AdminHub`, `ShopHub`, `DataSeeder`, `Persona`, `User`, `Setting`, and `PersonaInfo`. This change allows for more detailed user information. The `Name` field in the `Comment` type of the `OrderEntity` namespace has also been replaced with `Forename` to align with this change. Version numbers in `ShopHub`, `Persona`, and `User` classes have been updated. Tooltips and labels in the `Setting` component have been updated to reflect this change. Lastly, the `OrderGet` class now uses `Forename` instead of `Name` when creating comment objects.
Updated the `NewUser` method in `ShopHub` class to take `Surname` and `Forename` instead of `Name`. Updated `Migration` attribute in `20240304123656_Init.Designer.cs`. Replaced `Name` property with `Surname` and `Forename` in `Users` table across multiple files, with specific character limits and types. Added a new `Version` property to `Users` table as a concurrency token.
In this commit, the `Name` field in various classes and functions across multiple files (`Entity.cs`, `Info.tsx`, `Setting.tsx`, `Persona.tsx`, `Get.ts`, `Entity.ts`) has been replaced with `Surname` and `Forename` fields. This change in the data structure splits the name into two separate fields. In `Entity.cs`, an `Include` statement has been added to include the `User` in the query result when fetching comments. The display of the name in the `Label` and `ToastBody` components in `Info.tsx` and `Setting.tsx` has been updated to display the `Surname` followed by the `Forename`. In `Get.ts`, the `User` field in the `AdminOrderGet` class and the `Name` field in the `AdminUserGet` class have been replaced with `Forename`. The `name` variable in the `OrderGet` class is now assigned the value of `user.Forename` instead of `user.Name`. Finally, in `Entity.ts`, the `AdminUserEntity` class has been updated to version `0.2.0` and the `Name` field has been replaced with `Surname` and `Forename`.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.