Enhancement

Label names in chatwoot only support alphabets, numbers, hyphen and underscore.
At the moment the available validation doesn't show the user any errors, which would leave the user confused.

So let's add a validation error describing this behaviour

Current behaviour

<img width="1273" alt="Screenshot 2020-10-02 at 4 29 03 PM" src="https://user-images.githubuserconten

This demo is great and help us a lot.

As now JWT ( JSON Web Token ) becomes an important way of authentication. What bout adding JWT authentication to this demo? Or we use JWT authentication instead of traditional session-cookie way.

Let's make this demo more powerful. : )

Is your feature request related to a problem?

When sending incorrectly formatted payloads (e.g. a text-based string with a gzip compression header), the app will fail with a cryptic 500 error and register an unhandled exception.

Describe the solution you'd like

The app should return a 400 bad request error, with details on why the request failed (i.e. it is incorrectly formatted or

Problem
We need to be able to calculate how long it takes for a conversation to be closed ("resolved").

Right now the way we determine if a conversation is closed is by looking at the status field, which can currently only be "open" or "closed".

Solution

• Set up a database migration to add the closed_at field to the conversations table (as a utc_datetime)
• Update the

Context

• This is part of release-1.5 #148
• MEDIUM priority task

Tasks

• Remove dependency bcrypt-nodejs in package.json
• Add dependency bcrypt in package.json
• Migrate file app/data/user-dao.js to bcrypt
• Validate the instalation with the local test
• Add and submit the chang