[Bug] Dictionary GetValueByPath key access fails when the key is a integer or int as string.

[kle-sd]

Hey! Thanks for the great OSS library!

Running into a bug where I have a Dictionary<string, string> which fails when calling GetValueByPath due to the parsing thinking it is an array.

For example -

var dict = new Dictionary<string, string>
{
    ["1"] = "hello world"
};

// throws
var ex = dict.GetValueByPath("[1]");

Relevant code is here, I believe - https://github.com/iyulab/ObjectPath/blob/main/src/ObjectPath/ObjectPath.cs#L38-L41

[birdnamoo]

@kle-sd Thanks for the bug report!

Fixed in commit 48dc58d and will be available in v1.4.1.

Root Cause: Numeric segments (e.g., [1]) were always treated as array indices before checking if the object is a Dictionary.

Fix: Dictionary key lookup is now attempted first for numeric segments. If no matching key exists, it falls back to array index access.

// Now works correctly ✅
var dict = new Dictionary<string, string> { ["1"] = "hello world" };
var result = dict.GetValueByPath("[1]"); // Returns "hello world"

Workaround for older versions (< 1.4.1):

dict.GetValueByPath("[\"1\"]"); // String literal syntax

Added 21 test cases covering various numeric key scenarios including nested dictionaries, mixed dictionary/array access, and edge cases.

[kle-sd]

Thank you for the fix and super quick release 🙏