Data visualization

The following tests are outputting errant logs and warnings to the console during unit tests. Some of these are pointing out genuine errors and things that should be looked at, while others might be a bit more benign but should be cleaned up to make testing more pleasant.

In the future we may consider making console logs to be a failure condition in tests, so it would be good to sort these out

The Mixed Time-Series chart type allows for configuring the title of the primary and the secondary y-axis.
However, while only the title of the primary axis is shown next to the axis, the title of the secondary one is placed at the upper end of the axis where it gets hidden by bar values and zoom controls.

How to reproduce the bug

1. Create a mixed time-series chart
2. Configure axi

Summary

Aesthetically trivial, yet I've spotted a discrepancy with font sizes in our tooltip (front-end + back-end screenshots below).
I believe sections #1 and #2 should have the same font size?

![image](https://user-images.githubusercontent.com/27242399/139825179-4d62e3

Describe your context
Please provide us your environment, so we can easily reproduce the issue.

• replace the result of pip list | grep dash below

dash                      2.0.0
dash-bootstrap-components 1.0.0

• if frontend related, tell us your Browser, Version and OS

  • OS: [e.g. iOS] Windows
  • Browser [e.g. chrome, safari]: Chrome 96.0x, Edge 96.0x, Firefox

It was decided in the dev call today that we want to deprecate arrow() because of its awkward dependence on the axis scales. ...

As an alternative, we want to introduce a similar replacement vector(x, y, dx, dy, ...) where the parameters are still in data space, but the arrow shape is not tied to the data. This should be implemented based on FancyArrowPatch which is also the basis for `an

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

I haven't checked whether other options are missing.

缘由 Cause

G6 现在已经正式迈入了4.0+时代，我们很欣慰的看到有越来越多的人使用G6，承蒙各位厚爱，G6目前也在越来越多的场景被使用。与此同时，G6原来的图表案例就相形见绌了，还停留在一个比较基本的案例阶段，他只是展示了一些基本的原子功能案例。所以在这里，我们向社区的各位发出请求，为了让对G6的使用方案有更好的沉淀，希望大家提供自己实际的使用案例，我们将会修改为G6官网的案例，并且附上你的署名，让你的案例在G6官网可以帮助更多的人。

G6 has now officially entered the 4.0+ era and we are pleased to see that more and more people are using G6, and thanks to your love, G6 is now being used in more and

The variable columnNames is not available in Jython, whereas it is available in GREL. It is useful to iterate over all cells in a row, for instance with this expression:
forEach(row.columnNames,cn,cells[cn].value)
(see https://groups.google.com/g/openrefine/c/gV0bLUz7p7o)

Proposed solution

We could make this variable available in Jython too.
It would also be good to [document](https

Hi!

My suggestion/request is simple. When filtering the data, sometimes one needs to use the edge values of the data distribution in the filter histogram.

For example, one wants to choose the data of an hourly distribution (from 0:00 to 24:00) for the time between 22:00 and 6:00 in the nighttime and discard the data from 6:00 till 22:00 during the daytime.

So, when filtering the data with

• Base README.md
• Quizzes
• Introduction base README
  • Defining Data Science README
  • Defining Data Science assignment
  • Ethics README
  • Ethics assignment
  • Defining Data README
  • Defining Data assignment
  • Stats and Probability README
  • Stats and Probability assignment
• Working with Data base README
  • Rel

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

When entering a repository path, users should be able to hit TAB for autocomplete, like in bash.