add support to map sub items in an object to valuePath
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 351
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 1
Description
in cases where tables are not a single layered but have objects in some keys, but we want to display it in a single layer it would be better to support mappings to inner keys
for ex:
user = {
name: "something",
age: 10,
address: {
city: "somewhere",
country:"somewhere",
}}
if we want to display all this info in a table as a single layer, we right now cannot provide value paths like valuePath: "address.city"
adding support to this would be very useful
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how table columns currently resolve valuePath values, using the nested user example and the requested address.city path as the expected behavior. Done means nested object properties can be displayed as a single table layer through valuePath, with coverage for the example case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100