[Feature request] Nested headers

Open
#48 2 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

The issue does not name any files, tests, or entry points. Start by locating the existing column-definition and header-rendering code, then compare its behavior with the linked Handsontable nested-header example; done should include multiple header levels rendered from nested column definitions.

Written by the indexing model from the issue text.

Description

Hi,

Thank you for your amazing project, this library looks very promising.

It would be so nice if we could create nested headers, i.e. several levels of headers with headers on top of children headers. See this example in Handsontable.

We could define these nested columns like this, for instance:

columns: [
    {
        name: 'Framework infos',
        nestedColumns: [
            { name: 'Framework name' },
            { name: 'GitHub Stars' },
            { name: 'Forks' }
        ]
    },
    {
        name: 'Actions',
        nestedColumns: [
            { name: 'Project Link', format: value => `<a class="text-primary" href="${value}">${value}</a>` },
            { name: 'Fork', format: value => `<a class="text-primary" href="${value}">${value}</a>` }
        ]
    }
]

Are contributions welcome? I may submit a PR if you think this is an interesting feature.

Dominant language
JavaScript
Stars
1.3k
Forks
223
Avg merge
23h 14m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from frappe/datatable

All issues in frappe/datatable

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.