feat: support custom names in experimental_namedTuples register option #293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The current
experimental_namedTuplesfeature is useful for displaying tuple names in args. However, it currently includes names above a certain frequency threshold. While this covers most cases, there are situations where less common parameter names are used.For example,
toChainIdandtoAddressexist in the lookup, butfromChainIdandfromAddressdon't. This PR allows users to add custom names to handle these cases, as well as any project-specific parameter names.Changes
experimental_namedTuplestype frombooleantoboolean | readonly string[]We can use it like this: