Skip to content

feat(marker): add relativeTo option for specifying the relative target of marker position #20166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Apr 10, 2025

Conversation

Ovilia
Copy link
Contributor

@Ovilia Ovilia commented Jul 16, 2024

Brief Information

This pull request is in the type of:

  • bug fixing
  • new feature
  • others

What does this PR do?

Enhance the ability of markerPoint so that we can do more for stock charts.

image

Fixed issues

#19578

Details

Before: What was the problem?

We can only set the position of markPoints according to the whole canvas, but not to the grid area in pixels.

After: How does it behave after the fixing?

With relativeTo: 'coordinate', we can set the position in pixels according to the grid area.

Document Info

New API: markPoint.data.relativeTo: 'container' | 'coordinate'

  • container (default): relative to the whole canvas/svg container
  • coordinate: relative to the grid area

One of the following should be checked.

  • This PR doesn't relate to document changes
  • The document should be updated later
  • The document changes have been made in apache/echarts-doc@d1c2beb

Misc

ZRender Changes

  • This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs

N.A.

Others

Merging options

  • Please squash the commits into a single one when merging.

Other information

Copy link

echarts-bot bot commented Jul 16, 2024

Thanks for your contribution!
The community will review it ASAP. In the meanwhile, please checkout the coding standard and Wiki about How to make a pull request.

The pull request is marked to be PR: author is committer because you are a committer of this project.

⚠️ MISSING DOCUMENT INFO: Please make sure one of the document options are checked in this PR's description. Search "Document Info" in the description of this PR. This should be done either by the author or the reviewers of the PR.

@Ovilia Ovilia changed the base branch from master to v6 July 16, 2024 09:16
Copy link
Contributor

github-actions bot commented Jul 16, 2024

The changes brought by this PR can be previewed at: https://echarts.apache.org/examples/editor?version=PR-20166@beb3636

@echarts-bot echarts-bot bot added the PR: awaiting doc Document changes is required for this PR. label Jul 25, 2024
Copy link

echarts-bot bot commented Jul 25, 2024

Document changes are required in this PR. Please also make a PR to apache/echarts-doc for document changes and update the issue id in the PR description. When the doc PR is merged, the maintainers will remove the PR: awaiting doc label.

@Ovilia Ovilia marked this pull request as ready for review July 25, 2024 11:38
@Ovilia Ovilia added this to the 6.0.0 milestone Jul 25, 2024
@plainheart plainheart changed the title (feat): marker upgrade for stock charts feat(marker): add relativeTo option for specifying the relative target of marker position Apr 10, 2025
@plainheart plainheart merged commit 2b0bd9a into v6 Apr 10, 2025
2 checks passed
Copy link

echarts-bot bot commented Apr 10, 2025

Congratulations! Your PR has been merged. Thanks for your contribution! 👍

@plainheart plainheart deleted the feat/stock-marker branch April 10, 2025 11:43
@Ovilia Ovilia moved this to Done in ECharts 6.0 Apr 11, 2025
Ovilia added a commit that referenced this pull request Jun 18, 2025
@Ovilia Ovilia mentioned this pull request Jun 18, 2025
8 tasks
Ovilia added a commit that referenced this pull request Jun 19, 2025
Ovilia added a commit to apache/echarts-doc that referenced this pull request Jul 1, 2025
@echarts-bot echarts-bot bot added PR: doc ready and removed PR: awaiting doc Document changes is required for this PR. labels Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants