Regions replace does not work in regions API
See original GitHub issueThe regions API has a method for replacing regions:
chart.regions([
{axis: 'x', start: 5, class: 'regionX'},
{axis: 'y', end: 50, class: 'regionY'}
]);
In practice, this only seems to work for initializing a region (cf. regions.add()
), but not updating a region. E.g. in this fiddle, the first setTimeOut function will set a region, the second one does nothing.
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Regions and Amazon SES - Amazon Simple Email Service
Amazon SES is available in several AWS Regions around the world. In each Region, AWS maintains multiple Availability Zones. These Availability Zones are...
Read more >Working with Regions | Keyhole Markup Language
A Region affects visibility of a Placemark's geometry or an Overlay's image. Regions define both culling and level-of-detail behavior of the affected geometry ......
Read more >describe-regions — AWS CLI 2.9.11 Command Reference
Describes the Regions that are enabled for your account, or all Regions. For a list of the Regions supported by Amazon EC2, see...
Read more >How do I order a replacement card? - Regions Bank
Need to replace a lost, stolen or damaged card? Visit our FAQs page for information on requesting a replacement card or contact Card...
Read more >General Concepts | HTTP API - commercetools documentation
User accounts created for one Region are not valid for other Regions. ... {region}.commercetools.com , replace the {region} placeholder with the actual ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You can push the g parent elements data down to the rect element by doing .select rather than .selectAll (it’s a little-known d3 effect that often causes errors rather than solves them)
Since there’s only 1 rect per group element there’s no problem with not using .selectAll
becomes
regions = $$.mainRegion.select('rect'),
Having this problem still as well.