ryczko / formslab Goto Github PK

In the future, we will want to support several languages, and give users the ability to change them.

In the first step, we need to add and configure i18n, and transfer all texts to the en.json file.

Consider implementing Socket.IO to replace the refresh button on /survey/answer/:id

In order to reduce spam, we need to block the ability to send responses to the same survey from one device.

When implementing, we should use localStorage. You should create an array in it, e.g. answeredSurveys and store all ids of surveys that user answered. When user is sending answer we should check if the surveys is in array and if it is block an action (eg. navigate to home page with toast ‘you already answered in the survey’)

This solution will not guarantee sending several replies by the user (the user can always switch to Incognito mode or clear the browser's memory), but it will only limit this possibility, but because at the moment we do not require logging in to send replies, this is the only solution.

On the survey results page, the user should only be able to view responses with selected emojis.

For this purpose, we should create a multiselect component containing all selected emojis and display responses in accordance with the selected values.

Add error handling for the entire application

Better UX will be to add hot-toast message instead of logging it in console.

Example:
While creating an account with email which is already in use we got only error log in console.

Add storybook for each component

Deleting accounts does not work properly for now.

If you go to settingsManager file in handleOnAccountDelete you will notice that user.delete() will not working when user is logged to account since long time. To fix this we need reauthorize user after confirming the deletion of the account. We need display correct authorization method in the modal and after that remove account.

To see settings and delete account option you need to add NEXT_PUBLIC_REMOVE_ACCOUNT=TRUE to your .env file.

Add the ability to filter responses:

• displaying answers only with additional comment
• displaying answers only with a specific emoticon

Backdrop displayed when user is selecting emoji should be the same as when for example user is removing survey. It should also displaying and disappearing smoothly.

On the page with survey results, the user should be able to view only answers with additional feedback

For this purpose, we should create a checkbox that will allow displaying only such answers.

When creating a survey, we should give the option to edit the number of emoticons to choose from.
Minimum Quantity: 2
Maximum amount: 8
Example design during creation:

For now our logo is just a text with special font. This task is about creating the same logo using svg file and use it in all places. Also, remember about responsiveness.

Add pagination to my surveys page using usePagination hook. Similarly to how it is done on surveys answers page.

Sometimes components take a long time to load. To improve the user experience, we should display a progressbar informing about the progress of loading a new page. This will be especially useful when you want to fetch data using getServerSideProps.

In case of problems you can follow this article: https://blog.logrocket.com/how-to-build-a-progress-bar-indicator-in-next-js/

Show switch when answers > 0

At the moment, I can only remove it on the page displaying all polls. The user should also be able to delete a poll on the poll's response page.

We need to create an instruction for contributors describing the process of starting the project locally and creating contributions

On survey creation page currently, when the user does not enter a title, the create button is blocked, but the user is not informed why.

After the user starts completing the input and leaves it empty or clicks the create input button, we should display a message, e.g. add a red border and text with information that the field is required.

If necessary, we can use an external library. It would be good to create a solution that will allow you to easily extend validation in the future, for example, when we will want to validate other fields.

Steps to reproduce:

1. Create an account using your Google or Github account
2. Log out
3. Log in using Google or Github (Choose a different method than when creating the account for the first time) - the created account on the site must have the same email address.

Currently, the application does not allow to log in and throws an error in the console.
If the account already exists, it should be linked to the existing account when logging in.

Configure testing tools

When creating a survey, the user should be able to select an option that will force the user to complete the "tell us more" field when answering:

Create page should use Toggle component from shared folder

On the survey page, the user should be able to activate or deactivate the survey. A survey that is deactivated should not accept responses from users and inform that the survey is not active. Example desing:

That option should use Toggle component from shared folder.

Inactive surveys in the list of surveys should be distinguished, for example, with a red background

There can be many answers to one survey. We don't need to display them all on one page. We should enable pagination and display e.g. 20 answers on each page.

At the moment, we only limit the number of displayed components on the page, not the number of answers downloaded from the database.

It would be nice if the pagination functionality was reusable.

For now on answer page user can see disabled send button when none of emoji are selected.
The button should not be disabled and when clicked it should display a message in the emoji box that the user must select one.

We need to add the ability to delete an account by the user. After removing him, all polls created by him should also be deleted.

This option should be in the 'Setting' tab in the drop-down menu. If the bookmark has not been created in the meantime, it should be added as part of this task

Fix scrolling on pages with smaller height.
Remove github corner on device smaller than 300px

While creating a new account, a password consisting of only spaces is also accepted as a password

Emoji library used in our project provided component. Thanks to that we don’t need more use native emojis and provide the same emoji for all platforms.

I want to delete employee-pulse.vercel.app account.

We need change eslint and tsconfig to reduce potential bugs in the future.
For this, the most important for us is to remove all @typescript-eslint rulses from eslint that are set to 'off', and set strict: true in tsconfig.