I noticed that @NitronR has added a ton of content to mostly the rosetta code section (thanks BTW). You can see a list of his PR's here. I did forum search for a couple of the challenges and it looks like guide pages have been created, but I noticed that the forumTopicId wasn't added to many of the chall

注意：这里只处理 FreeCodeCamp.cn 的相关问题，不处理 w3cschool 的任何问题

注意：请不要乱开无意义的 Issue，违者直接加黑名单

注意：Issue 是用来处理代码库中的 bug，不是用来提问题的。完成挑战过程中遇到的代码问题请在gitter 讨论组 或者 QQ 群 526289580 中讨论 (QQ 群验证答案: freeCodeCamp 注意大小写)

FreeCodeCamp.cn Issue 模板

如何使用本模板:

• 尽可能多填些相关信息，方便管理员参考
• 对于无法给出的内容，请删除掉那一行

以上内容请在提交 Issue 之前删除

浏览器信息

• 浏览器名称，版本号
• 操作系统

Whenever a function is referenced in a prop type, such as label: Boolean | Object | ReactElement | Function [optional], there is no mention of what parameters the function receives, nor what the function should return. This is crucial information for anyone using the library. A solution should be determined for how to document these functions so that PRs can be opened for them. Should the word "

cc: plotly/plotly.js#4707 (comment)

The y-axis ticks supports the rotated option, but the doc is missing.

I haven't checked whether other options are missing.

The new (v5.8) Vega heatmap and isocontour transform requires "raster grids (matrices)"
input data format as seen in these Vega example data files:

 https://github.com/vega/vega/blob/master/docs/data/volcano.json
 https://github.com/vega/vega/blob/master/docs/data/annual-precip.json

It would be helpful to add explanation of this data format in the documentation:

  https://v

Checklist

• This is not a victory-native specific issue. (Issues that only appear in victory-native should be opened here)

• I have read through the FAQ and Guides before asking a question

• I am usi

There is a @vx/event package but it has no description or examples. It might be helpful to add some documentation for it.

fig.append_trace() raises ValueError if the row arg is not type int, even if arg is int-like:
DEBUG row:1, type(row):<class 'numpy.int64'>

If I explicitly cast to int with row=int(row), all is well. The issue may be due to the isinstance check at line 1536 of basedatatypes.py?

/usr/local/lib/python3.7/site-packages/plotly/basedatatypes.py in _validate_rows_cols(name, n, vals)
1535

I'm running into an issue with the hover details on bar graphs (but only in Firefox). Here's a fiddle I adjusted to show the issue - notice how the hover details flicker along the left edge of the graph rather than following the mouse.

Is it possible to use a gradient fill instead of a single colour?

var def = svg.append('defs');
var gradient = def.append('linearGradient')
    .attr('id', 'custom_id_1')
    .attr('x1', '50%')
    .attr('y1', '0%')
    .attr('x2', '50%')
    .attr('y2', '100%');

//set start
gradient.append('stop')
    .attr('offset', '0%')
    .attr('stop-color', 'white')

//set color at the

能否在config.js内添加更强大的自定义功能？

例如控制数据条宽度、数据条左侧文字大小、数据条右侧文字大小、数据条内部文字大小、数据条与数据条之间上下间隔大小等功能，这些功能在数据条目少，或者一屏多个并行动态排名下会非常有用

虽然我可以通过修改stylesheet.css和visual.js实现上述功能，但是我觉得其他人也可能会有这样的需求

Description

When setting zoom to the type drag, setting the extent and x.min/x.max properties seems to have no effect. They work when using the wheel type of zoom.

Steps to check or reproduce

Try using this with a chart (e.g. the one in https://naver.github.io/billboard.js/demo/#Interaction.Zoom) and you will see you are still able to zoom in as far as you like with the drag type, but a

This is pretty self explanatory, but code runtimes show with many decimal places on the UI. It would be nice to show only to the closest nanosecond or microsecond (perhaps this could be user selectable).

Is your feature request related to a problem? Please describe.
I've been unable to successfully implement curveBasis (or any other d3 curve function) with the curve input for ngx-charts-line-chart. There is a real lack of documentation for proper use. When trying to import d3 or d3-shape, I get typescript errors like this:

Expected Behavior

The tooltip height should be enough as for 3 values in the tooltip list, so as for 20 values.

Current Behavior

You have a great documentation on how to write an extension for V1. I've just started and think it would be better to start off with V2 directly.

However there is no documentation like this.
Maybe you could create one? :)

What likely needs to happen:

1. Docs moved inside of package (OR linked via setuptools)
2. Docs read and imported via python
3. Docs then parsed and available on a per-widget basis.

The ultimate goal of the above is so that there is never any disconnect between docs and UI. It should always stay in sync.

Hi, thanks for your greate work.
I'm a typescript user and use webpack to bundle my project files.
The webpack@2 has the Tree Shaking features which can reduce the size of files.
Since this feature can only work on es6, can you include the source code (the ts code are ok because I can use ts-loader to convert them), other than the production code in the npm package?

Here "there is no documentation available" when perhaps instead there should be some link to https://wiki.openstreetmap.org/wiki/Key:bridge etc.

Yes, there is no wiki "Structure" article. Therefore perhaps each subitem needs an "i" link.

The new docs are great but I think they would benefit if a search box was added? Would be useful to quickly look up stuff. :)

Bugs and Questions

Checklist

• This is a victory-native specific issue. (Issues that also appear in victory should be opened here)

• I have read through the FAQ and Guides before asking a question

• [x]

What is the problem?

YAxis labels do not render

When does it happen?

when react-native-svg is in version 12.
It does work up to version 11.0.1

What platform?

• iOS
• Android

react-native version: 0.62.0
react-native-svg-charts version: 5.3.0
react-native-svg version: 12.0.3

Code to reproduce

Change rn-svg version to 12.0.0 in the snack below

How would you recommend fixing negative values in barChar? I can't explain properly, so I'll show you an example:

2010: 0+0+0+0
2011: 0+0+0+0
2012: 0+0+0+0
2013: 0+5+8+0
2014: -38+0+13+0
2015: 45+12+130+0
2016: 0+0+0+0

I think that the xAxis should stay in y=0, and the

While working on #2160, I discovered that the FAQ answers linked from other answers only get into focus in mobile views - on full desktop views, the answers open up but they are not brought into the viewport if they were outside of it.