2025-03-17 User Detail - Revision history

Sven the Barbarian: Sven the Barbarian moved page 2025-034-17 User Detial to 2025-03-17 User Detail

2025-04-18T02:40:11Z

Sven the Barbarian moved page 2025-034-17 User Detial to 2025-03-17 User Detail

← Older revision	Revision as of 02:40, 18 April 2025
(No difference)

Pack at 08:39, 17 April 2025

2025-04-17T08:39:45Z

← Older revision		Revision as of 08:39, 17 April 2025
Line 4:		Line 4:
	*querry userId from backend if login and set it in local_storage.		*querry userId from backend if login and set it in local_storage.
	*use userId to querry user_detail.		*use userId to querry user_detail.
	*Must set ~~Uset~~-detal component as parent of menu-output.		*Must set User-detal component as parent of menu-output.

	=Why user-detail have to set as parent of menu-output=		=Why user-detail have to set as parent of menu-output=
Line 13:		Line 13:
	=Query userId=		=Query userId=
	==backend==		==backend==
	*Phee ~~is the one who~~ create api for get user-detail ask Phee if have problem with get userId.		*Phee create api for get user-detail ask Phee if have problem with get userId.
	*for query backen that have authentication require send header with query.		*for query backen that have authentication require send header with query.
	*Example		*Example

Pack at 08:37, 17 April 2025

2025-04-17T08:37:15Z

← Older revision		Revision as of 08:37, 17 April 2025
Line 7:		Line 7:

	=Why user-detail have to set as parent of menu-output=		=Why user-detail have to set as parent of menu-output=
	*Menu-~~output it~~ always mount on web page every ~~single~~ page will see menu~~-output that make~~ user~~-detail~~ component always mount ~~too~~.		*Menu-Output is always mount on the web page, so every page will see the output menu also makes the user details component always mount.
	*If user-detail not mount userdetail can't be query and if userdetail not query component will not know web page already login or not.		*If user-detail not mount userdetail can't be query and if userdetail not query component will not know web page already login or not.
	*After login menu-output will check login and decide which component should output between login component and not login component by check user detail had already query user-detail or not.		*After login menu-output will check login and decide which component should output between login component and not login component by check user detail had already query user-detail or not.

	=~~query~~ userId=		=Query userId=
	==backend==		==backend==
	*Phee is the one who create api for get user-detail ask Phee if have problem with get userId.		*Phee is the one who create api for get user-detail ask Phee if have problem with get userId.

Pack at 08:31, 17 April 2025

2025-04-17T08:31:42Z

← Older revision		Revision as of 08:31, 17 April 2025
Line 1:		Line 1:
	=Concept=		=Concept & Process=
			*Use useSelecter isLogin in user-detail reducer for get trigger when login process is done
	*check if login by get access_token from local_storage.		*check if login by get access_token from local_storage.
	*querry userId from backend if login and set it in local_storage.		*querry userId from backend if login and set it in local_storage.

Pack at 08:28, 17 April 2025

2025-04-17T08:28:32Z

← Older revision		Revision as of 08:28, 17 April 2025
Line 1:		Line 1:
	=Concept=		=Concept=
	*check if login by get access_token from local_storage		*check if login by get access_token from local_storage.
	*querry userId from backend if login and set it in local_storage		*querry userId from backend if login and set it in local_storage.
	*use userId to querry user_detail		*use userId to querry user_detail.
	*Must set Uset-detal component as parent of menu-output		*Must set Uset-detal component as parent of menu-output.

	=Why user-detail have to set as parent of menu-output=		=Why user-detail have to set as parent of menu-output=
Line 12:		Line 12:
	=query userId=		=query userId=
	==backend==		==backend==
	*~~phee~~ is the one who create api for get user-detail ask ~~phee~~ if have problem with get userId		*Phee is the one who create api for get user-detail ask Phee if have problem with get userId.
	*for query backen that have authentication require send header with query		*for query backen that have authentication require send header with query.
	*Example		*Example
	<syntaxhighlight lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	const objBackend = {		const objBackend = {
	method: "GET",		method: "GET",
	url: "https://xpxz4ia541.execute-api.us-east-2.amazonaws.com/Test/baseUserId/get",//if phee re-deploy service api will change ask ~~phee~~ if can't connect to api.		url: "https://xpxz4ia541.execute-api.us-east-2.amazonaws.com/Test/baseUserId/get",//if phee re-deploy service api will change ask Phee if can't connect to api.
	headers: { //require for query api backen with auth.		headers: { //require for query api backen with auth.
	Authorization: "Bearer " + localStorage.getItem("access_token"),		Authorization: "Bearer " + localStorage.getItem("access_token"),
Line 27:		Line 27:
	};		};
	const { data: userIdData } = useGetUserIdQuery(objBackend, {		const { data: userIdData } = useGetUserIdQuery(objBackend, {
	skip://not query backend if condition true, It ~~the~~ good way ~~for~~ set condition for query		skip://not query backend if condition true, It good way to set condition for query.
	!localStorage.getItem("access_token") \|\|		!localStorage.getItem("access_token") \|\|
	(localStorage.getItem("access_token") && localStorage.getItem("userId")),		(localStorage.getItem("access_token") && localStorage.getItem("userId")),
	});		});

			</syntaxhighlight>
			*backend have to give cors policy to allow frontend can get backend if see erro about cors policy ask Phee set this.
			<syntaxhighlight lang="JavaScript">
			"headers": {
			"Access-Control-Allow-Origin": "*",
			"Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, OPTIONS",
			"Access-Control-Allow-Headers": "Content-Type, Authorization"
			},
	</syntaxhighlight>		</syntaxhighlight>

Pack at 08:24, 17 April 2025

2025-04-17T08:24:48Z

@@ Line 3: / Line 3: @@
 *querry userId from backend if login and set it in local_storage
 *use userId to querry user_detail
-*Must to set Uset-detal component as parent of menu-output
+*Must set Uset-detal component as parent of menu-output
 =Why user-detail have to set as parent of menu-output=
-*Menu-output it always mount on web page every single page will see menu-output.
+*Menu-output it always mount on web page every single page will see menu-output that make user-detail component always mount too.
 *After login menu-output will check login and decide which component should output between login component and not login component by check user detail had already query user-detail or not.

Pack at 08:11, 17 April 2025

2025-04-17T08:11:58Z

← Older revision		Revision as of 08:11, 17 April 2025
Line 1:		Line 1:
	=Concept=		=Concept=
			*check if login by get access_token from local_storage
			*querry userId from backend if login and set it in local_storage
			*use userId to querry user_detail
			*Must to set Uset-detal component as parent of menu-output

			=Why user-detail have to set as parent of menu-output=
			*Menu-output it always mount on web page every single page will see menu-output.
			*After login menu-output will check login and decide which component should output between login component and not login component by check user detail had already query user-detail or not.

Pack: Created page with "=Concept="

2025-04-17T07:22:59Z

Created page with "=Concept="

New page

=Concept=