m-facey / formjam Goto Github PK

Description

Once the functionality for the profile page is added, we need to write some cypress test to ensure the functionality works as expected.

This is related to #28

Description

We need to add a section where the validation config for each question can be added. Please Note: there are various kinds of validation configs which differ based on question type,

• #23
• #24
• #25
• #26
• #27

Types of validations

• Number
  • Greater than
  • Greater than or equal to
  • Less than
  • Less than or equal to
  • Equal to
  • Not equal to
  • Between
  • Not between
  • Is number
  • Whole Number
• Text
  • Contains
  • Doesn't contain
  • Email
  • URL
• Length
  • Maximum character count
  • Minimum character count
• Regular Expression
  • Contains
  • Doesn't contains
  • Matches
  • Doesn't match

Type of validations

• Select at least
• Select at most
• Select exactly

Type of validations

• Length
  • Maximum character count
  • Minimum character count
• Regular Expression
  • Contains
  • Doesn't contains
  • Matches
  • Doesn't match

Description

We need to be able to duplicate question when creating a form. When a question is duplicated, it should be placed directly below the original.

Collab with @M-Facey to get more info to finish this.

Description

We should change the title of the page depending on what page it is. Here is a list of the rough idea of what they should be (please note: you can change them if you think you have a more appropriate name)

Most pages will have just be the <name_of_page> | FormJAM, however, the create / edit form page is an exception as it will use <form_title> | FormJAM

Description

The preview section has been implemented on this route, /form/:id/view?preview=true. We need to implement the functionality for when the user actually tries to submit a form.

Things to do

1. We need to generate a unique id for each form submission. This should be sorted inside local storage.
2. Add validation using vee-validate and yup somehow
3. Regenerate unique id from form, is there want to submit another one

To be done later

• We need to implement a step form cuz why not?

Description

Due to how the test was written, a lot of unused form will be created without getting deleted. We need to find a way to minimize its impact by either:

• #33
• Allow for bulk deletion of forms

hye, thanks for the project !!
Could you push the pb-schema.json from pocketbase...
better than deduce the schema from types... thanks

We need to make the form pages responsive and theme friendly.

Description

We should add functionality to the profile page, which is inclusive of the following:

Endpoints

How to update the profile info (including the password)

// example update data
const data = {
    "username": "test_username_update",
    "emailVisibility": false,
    "password": "87654321",
    "passwordConfirm": "87654321",
    "oldPassword": "12345678",
    "name": "test"
};

const record = await pb.collection('users').update('RECORD_ID', data);

How to delete the user profile

await pb.collection('users').delete('RECORD_ID');

You should use the useConfirm (this is for the delete modal) and useToast (this is for the pop up notification) services from primevue, which you can find in the Form Card component

Validations

Please look how validation is done using vee-validate in the Signup.vue. Please note: The name attributes used to reference to input elements.

Description

The forgot password (aka reset password) flow consists of two steps.

1. Password Reset - This is where the user send a reset password link and instruction to their email.
2. Confirm (New) Password - This is where the user enters their new password.

In order to test these, the request need to be intercepted and mocked. Please see the intercept docs on cypress for more information.