{
  "context": "This criteria evaluates how well the engineer uses the oauth-sign package's RFC 3986 percent-encoding capability to build a URL parameter encoder. The focus is on proper usage of the rfc3986 function for encoding strings and parameters according to RFC 3986 standards.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses rfc3986 function",
      "description": "The implementation imports and uses the rfc3986 function from the oauth-sign package for encoding strings",
      "max_score": 35
    },
    {
      "name": "encodeRFC3986 implementation",
      "description": "The encodeRFC3986 function correctly delegates to oauth-sign's rfc3986 function to encode the input string",
      "max_score": 25
    },
    {
      "name": "Parameter encoding logic",
      "description": "The encodeParams function uses oauth-sign's rfc3986 function to encode both parameter keys and values when constructing the query string",
      "max_score": 25
    },
    {
      "name": "Special character handling",
      "description": "The solution correctly encodes the RFC 3986 special characters (!, *, (, ), ') by using oauth-sign's rfc3986 function rather than JavaScript's standard encodeURIComponent",
      "max_score": 15
    }
  ]
}