VisActor / VisActor/VChart

[Bug] 雷达图domainLine、label、tick等属性一定要设置{}才能显示

Open
#4,129 0 comments 0 reactions 1 assignee View on GitHub

@kkxxkk2019 is already working on this.

Since Aug 5, 2025.

bug
Dominant language
TypeScript
Stars
1.8k
Forks
221
Avg merge
1d 6h
Merged PRs (30d)
26

Description

Version

1.0.3

Link to Minimal Reproduction

1.0.3

Steps to Reproduce
复现demo

const spec = {
  type: 'radar',
  data: [
    {
      id: 'radarData',
      values: [
        {
          key: 'Strength',
          value: 5
        },
        {
          key: 'Speed',
          value: 5
        },
        {
          key: 'Shooting',
          value: 3
        },
        {
          key: 'Endurance',
          value: 5
        },
        {
          key: 'Precision',
          value: 5
        },
        {
          key: 'Growth',
          value: 5
        }
      ]
    }
  ],
  categoryField: 'key',
  valueField: 'value',
  point: {
    visible: false // disable point
  },
  area: {
    visible: true, // display area
    state: {
      // The style in the hover state of the area
      hover: {
        fillOpacity: 0.5
      }
    }
  },
  line: {
    style: {
      lineWidth: 4
    }
  },
  axes: [
    {
      orient: 'radius', // radius axis
      // 不设置无法显示
      //label: {},
    }
  ]
};

const theme = {
  component: {
    axisRadius: {
      label: {
          visible: true,
      },
      domainLine: {
        visible: true,
      }
    },
  }
}

VChart.ThemeManager.registerTheme("simple", theme);
VChart.ThemeManager.setCurrentTheme("simple");

const vchart = new VChart(spec, { dom: CONTAINER_ID });
vchart.renderSync();

// Just for the convenience of console debugging, DO NOT COPY!
window['vchart'] = vchart;
Current Behavior

一定设置空对象才能显示

Expected Behavior

不设置空对象也能显示

Environment
- OS:
- Browser:
- Framework:
Any additional comments?

No response

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.