Refactor ArrayTransformations object
Open
Conformance
feature
priority: undecided
refactoring
under discussion
- Dominant language
- Scala
- Stars
- 33
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
## Background
`object ArrayTransformations` is hard to read & understand, there is a danger of field name clashes and code could be possibly optimized
## Feature
Refactor the `object ArrayTransformations` to address the issues:
* better functions and vals naming
* ensure used temporary field names are unique
* ensure when array fields are "brought to top level" their names are unique
* consider optimizations like repeated field name parsing
Contributor guide
Assessment
This issue has not been assessed yet.