An include option does not filter nested keys

[marcinrogacki]

Hi, I've notice that include option (-I) stops working when trying to filter by 2nd+ nested keys.

Version: 13.1.3

$ cat pino.log
{"level":20,"time":1772096544104,"pid":33,"hostname":"test","user":{"id":"1234","name":"Joe"},"request":{"ip":"127.0.0.1"},"msg":"User update"}
# Include shows nothing
$ cat pino.log | pino-pretty -I user.id
User update
# Ignore works as expected 
$ cat pino.log | pino-pretty -i user.id
[10:02:24.104] DEBUG (33 on test): User update
    user: {
      "name": "Joe"
    }
    request: {
      "ip": "127.0.0.1"
    }
# Include works fine on 1st level key
$ cat pino.log | pino-pretty -I user
User update
    user: {
      "id": "1234",
      "name": "Joe"
    }

[mcollina]

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.

[mahmoodhamdi]

I've submitted a PR to fix this: #648

The root cause is in filterLog — when using the include filter with nested keys like user.id, it does a direct property lookup (logCopy["user.id"]) instead of traversing the nested path (logCopy.user.id).

The fix adds a getNestedValue helper that walks the dot-separated path, and a setNestedValue helper that reconstructs only the matching nested structure in the filtered output. It also includes tests for nested key filtering with -I.