Request Auth Code Page
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description

Add the same fields as here

Request to Join -> **Launch Common**
Describe why we need this -> **We are looking for initiatives that are ready to launch and be our superusers as we design the product further.**
API: /notifications/send-email
https://daostack-common.postman.co/workspace/DAOStack~c27aebaf-5510-42be-97d7-2e9022d76953/request/18851081-b2a54cbf-bdfc-4b6f-a875-9bd7503c6c14
const schema = Yup.object().shape({
name: Yup.string().required(FORM_ERROR_MESSAGES.REQUIRED),
commonTitle: Yup.string().required(FORM_ERROR_MESSAGES.REQUIRED),
description: Yup.string().required(FORM_ERROR_MESSAGES.REQUIRED),
residence: Yup.string().required(FORM_ERROR_MESSAGES.REQUIRED),
email: Yup.string()
.email(FORM_ERROR_MESSAGES.EMAIL)
.required(FORM_ERROR_MESSAGES.REQUIRED),
phoneNumber: Yup.string()
.required(FORM_ERROR_MESSAGES.REQUIRED)
.test("isValidPhoneNumber", FORM_ERROR_MESSAGES.PHONE_NUMBER, (data = "") =>
isPossiblePhoneNumber(data)
),
});
export enum FORM_ERROR_MESSAGES {
REQUIRED = "This field is required",
LONG = "is too long",
SHORT = "is too short",
PASSWORDS_MATCH = "Passwords do not match",
NUMBER = "must be a number",
EMAIL = "Please enter a valid email",
UPPERCASE = "At least 1 uppercase letter",
LOWERCASE = "At least 1 lowercase letter",
DIGIT = "At least 1 digit",
ONLY_TEXT = "must be without numbers",
PHONE_NUMBER = "Please enter a valid phone number",
}
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing Request to Join page and the form integration for the /notifications/send-email API. Compare its fields and copy with the screenshots and the listed Yup schema. Done means a Request Auth Code page has the specified fields, validation messages, and sends the requested data through the email notification endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100