Albin Larsson
Albin Larsson
>>But it's confusing because we had https://github.com/OpenRefine/OpenRefine/pull/6725. Again this illustrates how problematic these meetings are. > >I agree that it was confusing for a few days. However, I think it...
> @Abbe98 that's not correct and maybe your mixing "extensions" with "distributions", maybe not? In that #6725 in the project's repo, looks like we only asked for authors of "extensions"...
The line-seperated GeoJSON export do work and might be a potential workaround for others.
Could it be that Docusaurus do no longer support `prefears-color-scheme`? Switching to dark mode manually fixes most of the issues(only the footer remains inaccessible).
> Okay I just found the Extract button in the History sidebar where one can save the transformation. If this does what I think it does is would be more...
PS this should not be squash merged.
I updated both commits to reflect your feedback @tfmorris. The only additional change is that I explicitly named the functions `*After` as the other menu extension points will need both...
There has previously been a proposal to add support for OpenTelemetry so that hosts and other distributors could hook OpenRefine usage data into existing tooling.
This is one instance: https://forum.openrefine.org/t/adding-error-reporting-with-sentry/816/4
Does this test anything OpenRefine specific? As I read it, it tests Apache Commons CSV.