metafacture/metafacture-flux

Xtext-based tool support for the Metafacture Flux language

metafacture-flux's Issues

Build new with UNIX

Analog to metafacture/metafacture-fix#315

The flux extension should be build newly with UNIX and it should be documented, that it should be only build with UNIX.

Escaped `"` break string syntax coloring

escaped " are not highlighted correctly.

Open VSX Listing: Sign the Publisher Agreement, package the license

See metafacture/metafacture-fix#41 for details.

The Publisher Agreement must be signed only once for each publisher (@katauber), but the license must be properly packaged with every extension.

Re-name repo?

I find it confusing that this repo is named "metafacture-flux" since this repo is not about the flux itself but a "Xtext-based tool support for the Metafacture Flux language".

Is renaming an option?

Content assist with available Flux commands + documentation

Move functionality from metafacture-ide: doc, ui, impl

To get all available Flux commands and details, see https://github.com/metafacture/metafacture-core/blob/master/metafacture-flux/src/main/java/org/metafacture/flux/HelpPrinter.java

Extracting the unmapped fields in separate JSON

While there is a fix-function map(_else) to take over all unmapped elements of a dataset, these elements are transferred to the same JSON file as all mapped elements.

Since both mapped and unmapped elements are in the same JSON-file it is difficult to read and to distinguish between them quickly.

A module would be great that creates a separate JSON with all unmapped elements.
Instead of a new module an alternative way would be if the fix-function map(_else) already triggers the creation of the separate JSON file.

Migrate to GitHub Actions

• migrate project from Travis CI to GitHub Actions.
• add workflow like metfacture fix deploy workflow to deploy the flux extension on the extensions landing page

See hbz/lobid#433

Integrate features from metafacture-ide

In the metafacture-ide Xtext project, we have some Flux UI features: https://github.com/culturegraph/metafacture-ide/tree/master/bundles/org.culturegraph.mf.ide.ui/src/org/culturegraph/mf/ide/ui

Some of these use implementation code in: https://github.com/culturegraph/metafacture-ide/tree/master/bundles/org.culturegraph.mf.ide/src/org/culturegraph/mf/ide

Two features are very useful for working with Flux:

• #6: Content assist with available Flux commands + documentation: doc, ui, impl
• Semantic/type-based validation of the Flux workflow structure/order: doc, impl

These are probably more nice-to-have:

• Outline view customization: doc, ui
• Launching support: doc, ui, impl
• Workflow visualization: doc, impl, based on an Xtend template and Graphviz. In a playground app (see https://github.com/metafacture/metafacture-fix/issues/19), a graph visualization based on vis.js like in hbz/lobid#427 (comment) could be easily created based on the Xtend template

We should create individual issues for these (some, like the visualization, might rather go into the new playground repo, some, like launching, into both). Will add links above as we proceed.