You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue
Classic variable names containing digits after the first character are considered invalid.
Expected
Classic variables names should follow the standards, e.g :
allow names like a1, a1a
refuse names like 1a.
How to reproduce
When defining my mesg.yml like this :
name: aws-sqsdescription: MESG Service to interact with AWS SQStasks:
send:
description: send a message to AWS SQSinputs:
accessKeyId:
type: Stringdescription: AWS access key IDsecretAccessKey:
type: Stringdescription: AWS secret access keyregion:
type: Stringdescription: AWS regionurl:
type: Stringdescription: url of the AWS SQS queue to which a message is sentbody:
type: Objectdescription: message body to sendoutputs:
success:
data:
MD5OfMessageBody:
type: Stringdescription: MD5 digest of the non-URL-encoded message bodyerror:
data:
message:
type: String
This very line triggers an error :
outputs:
success:
data:
MD5OfMessageBodytype: Stringdescription: MD5 digest of the non-URL-encoded message body
👉 MD5OfMessageBody
Error
The text was updated successfully, but these errors were encountered:
This problem has already been solved and is about to be released.
We've decided to accept numbers even when they are in front of the attribute to be more flexible.
You can find all the details in the issue #396 or the associated pull request #493.
Here is a very small issue :
Issue
Classic variable names containing digits after the first character are considered invalid.
Expected
Classic variables names should follow the standards, e.g :
a1
,a1a
1a
.How to reproduce
When defining my mesg.yml like this :
This very line triggers an error :
👉
MD5OfMessageBody
Error
The text was updated successfully, but these errors were encountered: