So far, fare_zone are only managed in 2 places in NTFS:

• In stops ( https://github.com/CanalTP/navitia/blob/dev/documentation/ntfs/ntfs_fr.md#stopstxt-requis ).
• In fares application conditions ( https://github.com/CanalTP/navitia/blob/dev/documentation/ntfs/ntfs_fare_extension_fr.md#farescsv-optionnel ).

No object is managed, we only deal with a fare_zone_id. So we use it as the name w

• Fix the height of examples
• If user wishes, they have the option to view the example in modal window

Definition of done; a clear overview of steps needed before we can go to prod exists and is communicated to the freeCodeCamp team.

The help shows URLs like

"apis": [
    {
      "url": "http://petstore.swagger.io/v2/swagger.json"
    },

On Windows, you can use a relative URL e.g. "url": "file://tmp/src/swagger-myapp.yaml" or an absolute one e.g. "url": "file:///c/Users/olivier/go/src/github.com/myrepo/myproject/tmp/src/swagger-myapp.yaml"
On Linux, you can use only an absolute one!
Thanks

We should have a tutorial showing:

• How to use grlc as webservice
• How to use grlc from a notebook

We need to add finnish translation to about.html (the info texts you see when enter the main site).

On the docs page for: Aliencube.AzureFunctions.Extensions.OpenApi

unable to find any namespaces that include the reference to AppSettings:

var settings = new AppSettings();

All other references are resolved. Is there another nuget package to include?

>>> import swaggerconformance
>>> client = swaggerconformance.client.Client('http://petstore.swagger.io/v2/swagger.json')
No success responses defined - allowing 200
No success responses defined - allowing 200
No success responses defined - allowing 200
No success responses defined - allowing 200
No success responses defined - allowing 200
Only 'default' response defined - allowing any

Judging by documentation, it is currently only possible to use the validator application-wide, immediately affecting all of the endpoints. It would be helpful to be able to attach middleware to specific endpoints with predefined swagger path already filled during instantiation.

This is useful for two scenarios:

1. Google Cloud Functions: while they seem to use Express under the hood and in gen

Problem occurs when setting Schema option "typeKey" with non "type" value. Seems that "type" is hardcoded in m2s for obtaining SchemaTypes.

Probably would be better to use schema.options.typeKey reference instead of hardcoded "type".