*******************>>> should be on
$(document).one('receivelexconfig', function onReceiveLexConfig() {
var localTimeZone;
try {
localTimeZone = JSON.stringify(
Intl.DateTimeFormat().resolvedOptions().timeZone
);
} catch (err) {
localTimeZone = JSON.stringify(
new Date().getTimezoneOffse

Would it be possible to have the regex parser support character classes like \w within other character classes? I had a regex pattern earlier that used the character class [0-9a-zA-Z_\.-], and I attempted to simplify it with [\w\.\-]. I didn't notice this library doesn't support doing that, and was wondering just how difficult that would be to implement. For the time being i'm just expanding

Documentation for options for parse error handling and recovery are nonexistent. When a parse error occurs, what happens? What options are available for handling this error? How can I provide custom behavior for the exception that is raised when a parse error occurs?

Among others, Angular and Polymer allow you to define custom elements.
This is not supported with lesscpy

example code:

customtag .values {
    list-style: none;
}

More info:

• Angular: https://docs.angularjs.org/guide/directive
• Polymer custom elements: https://customelements.io/

Flex has a directive %option caseless to lex tokens in a case insensitive way.

Is there currently a way (besides using regular expressions) to accomplish the same?

Hi terrenjpeterson

can you please provide us full docs on creating this kind of bots, it will be amazing for lex beginner out there-there is no good tutorial on amazon lex bot if you know the best premium lex chatbot tutorial also please suggest us.

I love this app, I would like to create one but am confusing on response card with lambda :(

While we don't currently support any NLU providers that include multi-intent, we should document how multi-intent providers could be testing using the existing tools.

厉害哦