{
  "context": "This criteria evaluates how effectively the engineer uses the pg (node-postgres) package's connection string parsing capabilities. The focus is on utilizing pg-connection-string or pg's built-in connection configuration parsing to handle various connection string formats.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses pg parsing",
      "description": "Uses pg's connection string parsing functionality (e.g., pg-connection-string's parse() function or pg.Client/pg.Pool constructor's built-in parsing) rather than implementing custom parsing logic",
      "max_score": 30
    },
    {
      "name": "Standard URL parsing",
      "description": "Correctly handles standard PostgreSQL connection URLs (postgresql:// and postgres:// protocols) with all components (user, password, host, port, database) by leveraging pg's URL parsing",
      "max_score": 20
    },
    {
      "name": "Query parameter handling",
      "description": "Correctly extracts query parameters from connection strings (e.g., sslmode, application_name, sslcert, sslkey) using pg's parameter parsing capabilities",
      "max_score": 20
    },
    {
      "name": "Unix socket support",
      "description": "Correctly handles Unix domain socket connection strings (both space-separated format and socket:// protocol) using pg's socket path detection",
      "max_score": 15
    },
    {
      "name": "URL decoding",
      "description": "Correctly handles URL-encoded characters in connection strings (particularly in passwords) by utilizing pg's built-in URL decoding",
      "max_score": 15
    }
  ]
}