From react docs

Note:
We recommend using React Testing Library which is designed to enable and encourage writing tests that use your components as the end users do.
Alternatively, Airbnb has released a testing utility called Enzyme, which makes it easy to assert, manipulate, and traverse your React Components’ output.

On average I have [count of commits] per file.

We should have a common format for describing tunes (series of beeps) across the different implementations in this repository. Extensive searching was done, a simple widespread standard was not found.

Following is proposed:

1. Simple text file
2. Each line represents a beep or a pause
   1. Column one is a positive integer number of milliseconds
   2. Column two is a positive integer freque

Current Behavior

Seems we have a little syntax error in our markdown file.

Expected Behavior

One should be able to copy paste the maven dependency.

Possible Solution

We should fix the part starting with ```xml which seems to me is ment to out

Since we now got reading routines for structured VTK meshes with PR nschloe/meshio#399, it would be nice to conserve the information about the structured mesh.

Therefor we could add the dataset dict form

https://github.com/nschloe/meshio/blob/07a88dae1a4d8037904074f6f0ac6f20a8bf5c82/meshio/vtk_io.py#L153

to the Mesh container. The dataset dict could be init

现在我们很多 project 的目录结构都是自己定义的比较随意的那种，nirvana api 检测不到任何 descriptor

现在的想法是能不能在 run server 的时候再来生成 api docs，那个时候是已经拿到了所有 descriptor 的，也少了 nirvana api 检测/收集 descriptor 的步骤，把这个做成一个 Configurer，需要的话可以配置在启动 server 的时候生成文档或者直接把文档页面自动注册到当前 server 里，可以直接访问，比如：

$ go run main.go

INFO  0830-17:59:34.608+08 config.go:309 | Listening on :8080
INFO  0830-17:59:35.126+08 nirvana.go:231 | 

In this example the generated table of contents doesn't link to the sections on the page, because the headers have anchor tags in them. These should be sanitized out.

For example, in the user guide for IK, link to relevant examples, videos, forum questions, etc. and vice-versa.

Hi all,

I don't get the tests running on my local machine.
I use ubuntu and pycharm as IDE.
Within the virtual environments for python2.7 and python 3.6 I installed the following:

pip install -e local/skrf/dir
pip install nose

Is it possible to write an instruction, how to setup the tests, in the development page or in the documentation?
I just saw that the travis ci uses conda

Hello there!

Please consider updating/expanding the documentation regarding input events.

Let me give you an example of what I mean:

I was trying out the picking/highlighting feature and largely followed one of the examples from here: https://xeokit.github.io/xeokit-sdk/examples/#picking_canvas_mesh_colorize

In the source, there's this line: