A language for describing resource-oriented APIs & turning them into Swagger or resource diagrams. Oriented around the concepts we want to expose in the APIs.
Apache License 2.0
23
stars
7
forks
source link
Comments claim "TEST" is the default environment for a server, but environment is required (can't be defaulted) #172
Comments in the grammar for the servers block claim the optionally defined "environment" attribute defaults to TEST, when in fact, the implementation defaults to PROD and the grammar requires an environment be specified.
Go to specs-draft/field-mapper and add a servers block with no environment set to api.reslang:
servers {
/REST
server = "https://api-staging.liveramp.com"
}
Generate the spec while specifying the TEST environment:
$ ./generate-specs.sh ./specs-draft/field-mapper/ --env TEST
master: Pulling from liveramp-eng/reslang
Digest: sha256:5dc87e0c713e444a780cf15c5ff9a2d4706a582f93eea365429fbecbf97c45bf
Status: Image is up to date for gcr.io/liveramp-eng/reslang:master
gcr.io/liveramp-eng/reslang:master
Reslang error: Problem parsing file /app/reslang/specs/field-mapper/api.reslang: Expected "/*", "//", "environment", or [ \t\r\n] but "}" found., location: 10, 1
Describe The Bug
Comments in the grammar for the
servers
block claim the optionally defined "environment" attribute defaults toTEST
, when in fact, the implementation defaults toPROD
and the grammar requires an environment be specified.TEST
.PROD
.?
.To Reproduce
Go to
specs-draft/field-mapper
and add a servers block with no environment set toapi.reslang
:Generate the spec while specifying the TEST environment:
Expected Behavior
Expect the spec to be generated.
Reslang Version
Master/Latest