VisActor / VisActor/VTable

[Documentation] 行汇总底部固定之后frame边框如何配置

Open
#4,576 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs
Dominant language
TypeScript
Stars
3.7k
Forks
486
Avg merge
1d 19h
Merged PRs (30d)
16

Description

Documentation Title or Section
theme: {
        defaultStyle: {
          borderLineWidth: 0
        },
        frameStyle: {
            borderColor: 'red',
            borderLineWidth: 0
        },
        cornerHeaderStyle: {
          frameStyle: {
            borderColor: 'blue',
            borderLineWidth: [2, 0, 1, 0]
          },
        },
        headerStyle: {
          frameStyle: {
            borderColor: 'blue',
            borderLineWidth: [2, 0, 1, 0]
          },
          borderColor: 'blue',
          // borderLineWidth: [1, 0, 0, 0]
        },
        rowHeaderStyle: {
          frameStyle: {
            borderColor: 'blue',
            borderLineWidth: [0, 0, 0, 0]
          }
        },

        bodyStyle: {
          frameStyle: {
            borderColor: 'blue',
            borderLineWidth: [0, 0, 0, 0]
          }
        },
        bottomFrozenStyle: {
            // borderLineWidth: [0, 0, 1, 0],
            frameStyle: {
                borderColor: 'red',
                borderLineWidth: [1, 0, 1, 0]
            }
        },
      }
Image
Issue Description or Suggestion

如上配置之后,行汇总单元格的边框文档里面找不到如何配置的方法

Contributor guide

Open the contributing guide

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.

Research direction

Start with the supplied theme configuration and screenshot to determine how borders for row-summary cells behave when the bottom row is frozen. Document the applicable configuration and its expected result, including the missing method for configuring the row-summary cell border. No source files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.