Cleanup test dir

test/md/MarkDownTransform.test.ts → test/odt_md/MarkDownTransform.test.ts

@@ -119,6 +119,12 @@ describe('MarkDownTransformTest', () => {
     assert.ok(compareTexts(testMarkdown, markdown, false));
   });
 
+  it('test ./code-links', async () => {
+    const testMarkdown = fs.readFileSync(__dirname + '/code-links.md').toString();
+    const markdown = await transformOdt('code-links');
+    assert.ok(compareTexts(testMarkdown, markdown, false));
+  });
+
 });
 
 async function transformOdt(id: string) {

test/odt_md/code-links.md

@@ -0,0 +1,3 @@
+Inline markdown test  
+[![Develop Server Deploy](https://github.com/mieweb/wikiGDrive/actions/workflows/DevelopServerDeploy.yml/badge.svg?branch=develop&event=push)](https://github.com/mieweb/wikiGDrive/actions/workflows/DevelopServerDeploy.yml) [![Prod Server Deploy](https://github.com/mieweb/wikiGDrive/actions/workflows/ProdServerDeploy.yml/badge.svg?branch=master&event=push)](https://github.com/mieweb/wikiGDrive/actions/workflows/ProdServerDeploy.yml)  
+End

test/md/list-indent.md → test/odt_md/list-indent.md

@@ -1,7 +1,7 @@
 1. If not already there, navigate to the <strong>Health Surveillance</strong> menu of the Control Panel.
 2. Using the information acquired in the Health Surveillance Matrix, begin entering the appropriate actions to each of the respective panels, as needed, clicking <strong>Add Panel</strong>. Otherwise, click <strong>Edit</strong> on an existing panel action to make any necessary changes.
-  
-![](10000201000004BE0000011D30E30AE192655040.png)  
+
+![](10000201000004BE0000011D30E30AE192655040.png)
 
 
 3. When adding action items to panels, the [Representative Event panel action](#tyjcwt) is usually added to the panel first. Fill out all of the necessary fields according to the information acquired in the Health Surveillance matrix, and click <strong>Submit</strong> to save the panel action to the panel.
@@ -21,8 +21,8 @@
    7. <strong>Trigger Date</strong>: On what date should the panel action trigger? Use the drop-down to select one of the following Trigger Dates:
       1. <strong>Date of Birth</strong>: Triggers the panel action on the panel member's date of birth, on a schedule determined by the starting age and frequency. Assumes the panel member's DOB has been captured in the chart demographics.
       2. <strong>Other Action (Triggered)</strong>: The Other Action (Triggered) trigger date allows users to trigger a panel action at the same time as another action item, indicated in this panel action. For example, an action to trigger an Audiogram may be for Entry, Routine, or Exit actions; if checked, other actions may use this panel action as a trigger. This option must be selected for the action to display in the Related Action list. The Related Action list displays when then Trigger Date is set to Other Action (Triggered) or Prior Action (Completed). Additionally, action items can be configured to trigger with the Representative Events, as needed, if that programming is utilized. This allows all action items to trigger together for a panel. Triggers with all the same date are usually tied to representative event.
-  
-      ![](100002010000033B00000036339CF669B6C2B512.png)  
+
+      ![](100002010000033B00000036339CF669B6C2B512.png)
 
       3. <strong>Point in Time</strong>: The Point in Time trigger date allows users to trigger an action item on the same day and month, each year (must be MM/DD format).
       4. <strong>Panel Expiration</strong>: Triggers on the expiration date specified in the panel status. Most panels will be configured with a representative event as the