An open API service indexing awesome lists of open source software.

https://github.com/itishermann/quillform-funnel-mvp


https://github.com/itishermann/quillform-funnel-mvp

Last synced: 4 months ago
JSON representation

Awesome Lists containing this project

README

        

# Funnel MVP
An attempt to use QuillForms to replace current onboarding process.

## App Requirements
- [x] The app should be able to create a form
- [ ] The app should be able to send the form data step by step to the api
- [x] The app should be able to display some kind of progress bar
- [x] The app should be able to display the some inputs conditionally
- [x] The form should be able to display a thank you message after the form is submitted
- [x] The app should be able to display a loading spinner when an action is being performed
- [x] The app should be able to display a message when an error occurs
- [ ] The app should be able to display an stripe credit card collection input
- [ ] The app should be able to display a date picker input
- [ ] The app should be able to display a phone number input
- [ ] The app should be able to display a calendar input with AM & PM options

## Dependencies
- pnpm
- node 20 LTS
- docker
- docker-compose (optional)

## Setup
1. Clone the repository
2. Run `pnpm install` at the root of the project
3. Run `pnpm funnel-onboard:dev` to start the development server
4. Run `pnpm funnel-onboard:build` to build the project localy without docker
5. Run `docker build -f ./apps/funnel-onboard/Dockerfile -t funnel-onboard-mvp:latest ./` at the root to build the project with docker.
Alternatively, you can run the script `build-funnel-onboard-docker.sh` in the script folder to build the project with docker.

## Encountered Issues
- [ ] Quillforms types are not available in the package.
Maybe the types are not included in the package or the package is not installed correctly.
- [ ] When building the project with docker, the build fails with the error `Module not found: Can't resolve 'tinyColor2'`
Refer to the `build-error.log` file for more information.
This may be due the fact that the package is not included in the lockfile when using the `turbo prune` command.