damn-api Twitter API Spec

twitter_api.json

{
  "host": "api.twitter.com",
  "api_groups": [
    {
      "name": "Timelines",
      "apis": [
        {
          "name": "GET statuses/public_timeline",
          "type": "json",
          "path": "/1/statuses/public_timeline.json",
          "method": "GET",
          "params": {
            "trim_user": "*boolean",
            "include_entities": "*boolean"
          }
        },
        {
          "name": "GET statuses/user_timeline",
          "type": "json",
          "path": "/1/statuses/user_timeline.json",
          "method": "GET",
          "params": {
            "screen_name": "*string",
            "count": "*number",
            "page": "*number"
          }
        }
      ]
    },
    {
      "name": "Tweets",
      "apis": [
        {
          "name": "GET statuses/show/:id",
          "type": "json",
          "path": "/1/statuses/show/:id.json",
          "method": "GET",
          "url_params": {
            "id": {
              "value": "*number",
              "required": true
            }
          },
          "params": {
            "trim_user": "*boolean",
            "include_entities": "*boolean"
          }
        }
      ]
    }
  ]
}

Another way maybe there's a need to specify some magic keyword for that, such as number, string, uuid, appkey.

If you really want a regexp, true|false or 0|1 can be.

I think the logic should be matching the value with magic keywords and the problem is what keywords we pick. How about we use JT's suggestion number, string, uuid, appkey and see what the final list is and later on replace them with some special symbols (maybe some prefix, i.e. ?number).

Just found that the problem of \\d becomes d eventually is because I haven't update the raw JSON path.