You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a usecase for parsing pnpm-lock.yaml files using this library. Unfortunately, PNPM does not really seem to be concerned with the spec when it comes to key-length (spec says 1024 is the max, pnpm emitted a key of length >1080 in one of my testcases).
Describe the solution you'd like
I'd love to have a new function on the DeserializerBuilder(), maybe something like .WithMaxKeyLength() that allows defining a larger than the default value when deserializing.
Describe alternatives you've considered
Shortening the keys myself with a regex replace or something like that - I don't have a requirement for accurate keys in this specific case at least not for the long ones
Opening an issue with pnpm to adhere to the spec but given that the keys are relevant for them for faster caching, I am not sure this will have much chance of actually going through
Is your feature request related to a problem? Please describe.
I have a usecase for parsing pnpm-lock.yaml files using this library. Unfortunately, PNPM does not really seem to be concerned with the spec when it comes to key-length (spec says 1024 is the max, pnpm emitted a key of length >1080 in one of my testcases).
Describe the solution you'd like
I'd love to have a new function on the
DeserializerBuilder()
, maybe something like.WithMaxKeyLength()
that allows defining a larger than the default value when deserializing.Describe alternatives you've considered
Additional context
Reprocase:
Error:
The text was updated successfully, but these errors were encountered: