Add enums, AuthService, and integrate backend registration endpoints
All checks were successful
Build frontend / build (push) Successful in 57s
All checks were successful
Build frontend / build (push) Successful in 57s
- Add separate enum files: BuildingType, PropertyStatus, BookingStatus, CommissionType, IdentityType, UserRole, City, LoginMethod, OwnerType, CustomerType - Add AuthService (addToken/getToken/deleteToken) - Update api.js: use AuthService, add Owner/Add and Customer/Add endpoints - Update login page to use AuthService for token storage - Rewrite owner register: 3-step flow with OwnerType dropdown, backend integration, OTP verification - Rewrite tenant register: 2-step flow with CustomerType dropdown, backend integration, OTP verification - Update homepage and property detail to use enums instead of hardcoded maps - Update AddPropertyForm to import from enums directly - Add console logs and status toasts linked to API response messages
This commit is contained in:
17
app/enums/CustomerType.js
Normal file
17
app/enums/CustomerType.js
Normal file
@ -0,0 +1,17 @@
|
||||
/**
|
||||
* CustomerType Enum
|
||||
* Backend values for customer sub-types
|
||||
* Used in: Customer registration (Customer/Add)
|
||||
*/
|
||||
const CustomerType = Object.freeze({
|
||||
PERSONAL: 'Personal',
|
||||
FAMILY: 'Family',
|
||||
});
|
||||
|
||||
// Map value → Arabic label
|
||||
const CustomerTypeLabels = Object.freeze({
|
||||
[CustomerType.PERSONAL]: 'شخصي',
|
||||
[CustomerType.FAMILY]: 'عائلي',
|
||||
});
|
||||
|
||||
export { CustomerType, CustomerTypeLabels };
|
||||
Reference in New Issue
Block a user