You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -122,11 +118,11 @@ <h2 id="using-metafacture-as-a-java-library">Using Metafacture as a Java library
122
118
<p>If you want to use Metafacture in your own Java projects all you need is to add some dependencies to your project. As of Metafacture 5, the single metafacture-core package has been replaced with a number of domain-specific packages. You can find the list of packages on <ahref="https://search.maven.org/search?q=g:org.metafacture">Maven Central</a>.</p>
123
119
<p>Alternatively, you can simply guess the package names from the top-level folders in the source code repository – they are the same.</p>
124
120
<p>For instance, if you want to use the <code>metafacture-io</code> library in your project, simply add the following dependency to your <code>pom.xml</code>:</p>
@@ -58,14 +53,14 @@ <h2 id="setup-a-vs-code-codium-extension">Setup a VS Code / Codium extension</h2
58
53
<h2id="usage">Usage</h2>
59
54
<h3id="flux">Flux</h3>
60
55
<p>After installing the IDE extension to VS Code / Codium open a Flux file, for example <ahref="https://gitlab.com/oersi/oersi-etl/-/blob/master/data/production/digill/digill-to-oersi.flux">this one</a>. It should look like this:</p>
<p>If you delete for example a necessary bracket you will see in the Problems section that the extension detects problems with the Flux file:</p>
63
-
<p><imgsrc="/img/digill-to-oersi_flux_problem.JPG" alt="Flux editor with problems" style="max-width:100%"/></p>
58
+
<p><imgsrc="./img/digill-to-oersi_flux_problem.JPG" alt="Flux editor with problems" style="max-width:100%"/></p>
64
59
<h3id="fix">Fix</h3>
65
60
<p>After installing the IDE extension to VS Code / Codium open a Flux file, for example <ahref="https://gitlab.com/oersi/oersi-etl/-/blob/master/data/production/digill/digill.fix">this one</a>. It should look like this:</p>
<p>If you remove a closing <code>end</code> you will see in the Problems section that the extension detects the missing <code>end</code>:</p>
68
-
<p><imgsrc="/img/digill_fix_problem.JPG" alt="Fix editor with problems" style="max-width:100%"/></p>
63
+
<p><imgsrc="./img/digill_fix_problem.JPG" alt="Fix editor with problems" style="max-width:100%"/></p>
69
64
<h2id="github">GitHub</h2>
70
65
<p>To report issues, see the code, and contribute to the projects, visit: <ahref="https://github.com/metafacture/metafacture-fix">Fix Repository</a>, <ahref="https://github.com/metafacture/metafacture-flux">Flux Repository</a>.</p>
@@ -22,21 +22,21 @@ There are different ways to install extensions for VS Code / Codium.
22
22
23
23
After installing the IDE extension to VS Code / Codium open a Flux file, for example [this one](https://gitlab.com/oersi/oersi-etl/-/blob/master/data/production/digill/digill-to-oersi.flux). It should look like this:
If you delete for example a necessary bracket you will see in the Problems section that the extension detects problems with the Flux file:
28
28
29
-
<imgsrc="/img/digill-to-oersi_flux_problem.JPG"alt="Flux editor with problems"style="max-width:100%"/>
29
+
<imgsrc="./img/digill-to-oersi_flux_problem.JPG"alt="Flux editor with problems"style="max-width:100%"/>
30
30
31
31
### Fix
32
32
33
33
After installing the IDE extension to VS Code / Codium open a Flux file, for example [this one](https://gitlab.com/oersi/oersi-etl/-/blob/master/data/production/digill/digill.fix). It should look like this:
0 commit comments