fix(types): add support for size and rename fieldtransformers #462
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.
Im not sure if we want to maintain or use this anymore - and we could probably get away by using our
zod
-schemas as a source of truth for the types...We recently used
size and rename
field transformers incategoryCombos/Edit
to get the number ofcategoryOptions
withincategory
. . This would cause the inferred type fromPickWithFieldFilters
to be incorrect. This should add support for ~rename and ~size field-transformers.original~rename(newName)
will rename the property in the type.~size
will cause the type of the property to be number. Note that there's no real validation on this, is just enforces the type to be number.categories[id,displayName]~rename(cat)
. This also does not work in the API, so it makes sense: http://localhost:8080/api/categoryCombos?fields=id,name,categories[id,name]~rename(cat)categories[id, displayName, categoryOptions~size~rename(optionSize)