@omegagrid/demo 0.4.14 → 0.4.15

package/dist/types/components/demoMarkdownEditor.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"demoMarkdownEditor.d.ts","sourceRoot":"","sources":["../../../src/components/demoMarkdownEditor.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAGrD,OAAO,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAEhD,OAAO,EAAE,MAAM,EAAE,MAAM,iBAAiB,CAAC;AAEzC,qBACa,kBAAmB,SAAQ,aAAa;IAEpD,MAAM,CAAC,MAAM,0BAcX;IAGF,MAAM,EAAE,cAAc,CAAC;IAEvB,SAAS,MAAO,OAAO,WAAW,UAGjC;IAED,SAAS,SAAgB,IAAI,KAAG,QAAQ,MAAM,CAAC,CAI9C;IAED,MAAM,6CAMJ;CAEF"}
+{"version":3,"file":"demoMarkdownEditor.d.ts","sourceRoot":"","sources":["../../../src/components/demoMarkdownEditor.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAGrD,OAAO,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAEhD,OAAO,EAAE,MAAM,EAAE,MAAM,iBAAiB,CAAC;AAEzC,qBACa,kBAAmB,SAAQ,aAAa;IAEpD,MAAM,CAAC,MAAM,0BAcX;IAGF,MAAM,EAAE,cAAc,CAAC;IAEvB,SAAS,MAAO,OAAO,WAAW,UAGjC;IAED,SAAS,SAAgB,IAAI,KAAG,QAAQ,MAAM,CAAC,CAI9C;IAED,MAAM,6CAOJ;CAEF"}

package/dist/types/components/demoMarkdownView.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"demoMarkdownView.d.ts","sourceRoot":"","sources":["../../../src/components/demoMarkdownView.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AAGtE,OAAO,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAGhD,qBACa,gBAAiB,SAAQ,aAAa;IAElD,MAAM,CAAC,MAAM,0BAoBX;IAGF,QAAQ,EAAE,YAAY,CAAC;IAEjB,YAAY;IAIlB,OAAO,MAAO,iBAAiB,UAW9B;IAED,MAAM,6CAIJ;CAEF"}
+{"version":3,"file":"demoMarkdownView.d.ts","sourceRoot":"","sources":["../../../src/components/demoMarkdownView.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,YAAY,EAAkB,MAAM,qBAAqB,CAAC;AAGtF,OAAO,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAQhD,qBACa,gBAAiB,SAAQ,aAAa;IAElD,MAAM,CAAC,MAAM,0BAoBX;IAGF,QAAQ,EAAE,YAAY,CAAC;IAEjB,YAAY;IAMlB,OAAO,MAAO,iBAAiB,UAW9B;IAED,MAAM,6CAKJ;CAEF"}

package/dist/types/data/gridDataFilters.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"gridDataFilters.d.ts","sourceRoot":"","sources":["../../../src/data/gridDataFilters.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,iBAAiB,CAAC;AAe7C,QAAA,MAAM,QAAQ,EAAE,UAoBf,CAAC;AAEF,eAAe,QAAQ,CAAC"}
+{"version":3,"file":"gridDataFilters.d.ts","sourceRoot":"","sources":["../../../src/data/gridDataFilters.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,iBAAiB,CAAC;AAkB7C,QAAA,MAAM,QAAQ,EAAE,UAyBf,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/dist/types/data/markdown1.d.ts

@@ -1,2 +1,2 @@
-export declare const markdown = "\n# Markdown: Syntax\n\n*   [Overview](#overview)\n    *   [Philosophy](#philosophy)\n    *   [Inline HTML](#html)\n    *   [Automatic Escaping for Special Characters](#autoescape)\n*   [Block Elements](#block)\n    *   [Paragraphs and Line Breaks](#p)\n    *   [Headers](#header)\n    *   [Blockquotes](#blockquote)\n    *   [Lists](#list)\n    *   [Code Blocks](#precode)\n    *   [Horizontal Rules](#hr)\n*   [Span Elements](#span)\n    *   [Links](#link)\n    *   [Emphasis](#em)\n    *   [Code](#code)\n    *   [Images](#img)\n*   [Miscellaneous](#misc)\n    *   [Backslash Escapes](#backslash)\n    *   [Automatic Links](#autolink)\n\n\n----\n\n```sql\ndeclare @delete_user_cursor cursor\nset @delete_user_cursor = cursor for\nselect distinct A.USER_NAME, A.LOGIN_NAME from {db_super}.dbo.V_ACCESS_ACCOUNT_RIGHT A\n\tjoin {db_super}.dbo.V_ACCESS_ACCOUNT B on B.USER_NAME = A.USER_NAME and B.ORIGIN = 'helios'\n\tleft join #users C on C.LOGIN_NAME = A.LOGIN_NAME\n\twhere A.ID_ACCOUNTING_GROUP = @id_accounting_group and C.LOGIN_NAME is null\n\nopen @delete_user_cursor\n\tfetch next from @delete_user_cursor into @user_name, @login_name\n\twhile @@fetch_status = 0 begin\n\t\tbegin try\n\t\t\texec {db_super}.dbo.p_DELETE_USER @user_name, @who_created\n\t\t\tset @message = concat('delete user ', @login_name, ' (', @user_name, ')')\n\t\t\texec {db_super}.dbo.p_journal @id_audit, @id_call output, @accounting, @dr, 'users', 'p_DELETE_USER', 'P_ACCESS_ACCOUNT', 0, 1, @message, 1;\n\t\tend try begin catch\n\t\t\tset @message = concat(@login_name, ': ', error_message())\n\t\t\texec {db_super}.dbo.p_journal @id_audit, @id_call output, @accounting, @dr, 'users', 'p_DELETE_USER', 'P_ACCESS_ACCOUNT', 1, 0, @message, 1;\n\t\tend catch\n\t\t\t\t\t\t\t\t\t   \n\t\tfetch next from @delete_user_cursor into @user_name, @login_name\n\tend\nclose @delete_user_cursor   \ndeallocate @delete_user_cursor\n```\n\n\n## Overview\n\n### Philosophy\n\nMarkdown is intended to be as easy-to-read and easy-to-write as is feasible.\n\nReadability, however, is emphasized above all else. A Markdown-formatted\ndocument should be publishable as-is, as plain text, without looking\nlike it's been marked up with tags or formatting instructions. While\nMarkdown's syntax has been influenced by several existing text-to-HTML\nfilters -- including [Setext](http://docutils.sourceforge.net/mirror/setext.html), [atx](http://www.aaronsw.com/2002/atx/), [Textile](http://textism.com/tools/textile/), [reStructuredText](http://docutils.sourceforge.net/rst.html),\n[Grutatext](http://www.triptico.com/software/grutatxt.html), and [EtText](http://ettext.taint.org/doc/) -- the single biggest source of\ninspiration for Markdown's syntax is the format of plain text email.\n\n## Block Elements\n\n### Images\n![1.00](https://milkdown.dev/polar.jpeg \"Hello by a polar bear\")\n\n### Paragraphs and Line Breaks\n\nA paragraph is simply one or more consecutive lines of text, separated\nby one or more blank lines. (A blank line is any line that looks like a\nblank line -- a line containing nothing but spaces or tabs is considered\nblank.) Normal paragraphs should not be indented with spaces or tabs.\n\nThe implication of the \"one or more consecutive lines of text\" rule is\nthat Markdown supports \"hard-wrapped\" text paragraphs. This differs\nsignificantly from most other text-to-HTML formatters (including Movable\nType's \"Convert Line Breaks\" option) which translate every line break\ncharacter in a paragraph into a `<br />` tag.\n\nWhen you *do* want to insert a `<br />` break tag using Markdown, you\nend a line with two or more spaces, then type return.\n\n### Headers\n\nMarkdown supports two styles of headers, [Setext] [1] and [atx] [2].\n\nOptionally, you may \"close\" atx-style headers. This is purely\ncosmetic -- you can use this if you think it looks better. The\nclosing hashes don't even need to match the number of hashes\nused to open the header. (The number of opening hashes\ndetermines the header level.)\n\n\n### Blockquotes\n\nMarkdown uses email-style `>` characters for blockquoting. If you're\nfamiliar with quoting passages of text in an email message, then you\nknow how to create a blockquote in Markdown. It looks best if you hard\nwrap the text and put a `>` before every line:\n\n> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\n> consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\n> Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\n> \n> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\n> id sem consectetuer libero luctus adipiscing.\n\nMarkdown allows you to be lazy and only put the `>` before the first\nline of a hard-wrapped paragraph:\n\n> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\nconsectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\nVestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\n\n> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\nid sem consectetuer libero luctus adipiscing.\n\nBlockquotes can be nested (i.e. a blockquote-in-a-blockquote) by\nadding additional levels of `>`:\n\n> This is the first level of quoting.\n>\n> > This is nested blockquote.\n>\n> Back to the first level.\n\nBlockquotes can contain other Markdown elements, including headers, lists,\nand code blocks:\n\n> ## This is a header.\n> \n> 1.   This is the first list item.\n> 2.   This is the second list item.\n> \n> Here's some example code:\n> \n>     return shell_exec(\"echo $input | $markdown_script\");\n\nAny decent text editor should make email-style quoting easy. For\nexample, with BBEdit, you can make a selection and choose Increase\nQuote Level from the Text menu.\n\n\n### Lists\n\nMarkdown supports ordered (numbered) and unordered (bulleted) lists.\n\nUnordered lists use asterisks, pluses, and hyphens -- interchangably\n-- as list markers:\n\n*   Red\n*   Green\n*   Blue\n\nis equivalent to:\n\n+   Red\n+   Green\n+   Blue\n\nand:\n\n-   Red\n-   Green\n-   Blue\n\nOrdered lists use numbers followed by periods:\n\n1.  Bird\n2.  McHale\n3.  Parish\n\nIt's important to note that the actual numbers you use to mark the\nlist have no effect on the HTML output Markdown produces. The HTML\nMarkdown produces from the above list is:\n\nIf you instead wrote the list in Markdown like this:\n\n1.  Bird\n1.  McHale\n1.  Parish\n\nor even:\n\n3. Bird\n1. McHale\n8. Parish\n\nyou'd get the exact same HTML output. The point is, if you want to,\nyou can use ordinal numbers in your ordered Markdown lists, so that\nthe numbers in your source match the numbers in your published HTML.\nBut if you want to be lazy, you don't have to.\n\nTo make lists look nice, you can wrap items with hanging indents:\n\n*   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\n    Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\n    viverra nec, fringilla in, laoreet vitae, risus.\n*   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\n    Suspendisse id sem consectetuer libero luctus adipiscing.\n\nBut if you want to be lazy, you don't have to:\n\n*   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\nAliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\nviverra nec, fringilla in, laoreet vitae, risus.\n*   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\nSuspendisse id sem consectetuer libero luctus adipiscing.\n\nList items may consist of multiple paragraphs. Each subsequent\nparagraph in a list item must be indented by either 4 spaces\nor one tab:\n\n1.  This is a list item with two paragraphs. Lorem ipsum dolor\n    sit amet, consectetuer adipiscing elit. Aliquam hendrerit\n    mi posuere lectus.\n\n    Vestibulum enim wisi, viverra nec, fringilla in, laoreet\n    vitae, risus. Donec sit amet nisl. Aliquam semper ipsum\n    sit amet velit.\n\n2.  Suspendisse id sem consectetuer libero luctus adipiscing.\n\nIt looks nice if you indent every line of the subsequent\nparagraphs, but here again, Markdown will allow you to be\nlazy:\n\n*   This is a list item with two paragraphs.\n\n    This is the second paragraph in the list item. You're\nonly required to indent the first line. Lorem ipsum dolor\nsit amet, consectetuer adipiscing elit.\n\n*   Another item in the same list.\n\nTo put a blockquote within a list item, the blockquote's `>`\ndelimiters need to be indented:\n\n*   A list item with a blockquote:\n\n    > This is a blockquote\n    > inside a list item.\n\nTo put a code block within a list item, the code block needs\nto be indented *twice* -- 8 spaces or two tabs:\n\n*   A list item with a code block:\n\n        <code goes here>\n\n### Code Blocks\n\nPre-formatted code blocks are used for writing about programming or\nmarkup source code. Rather than forming normal paragraphs, the lines\nof a code block are interpreted literally. Markdown wraps a code block\nin both `<pre>` and `<code>` tags.\n\nTo produce a code block in Markdown, simply indent every line of the\nblock by at least 4 spaces or 1 tab.\n\nThis is a normal paragraph:\n\n    This is a code block.\n\nHere is an example of AppleScript:\n\n    tell application \"Foo\"\n        beep\n    end tell\n\nA code block continues until it reaches a line that is not indented\n(or the end of the article).\n\nWithin a code block, ampersands (`&`) and angle brackets (`<` and `>`)\nare automatically converted into HTML entities. This makes it very\neasy to include example HTML source code using Markdown -- just paste\nit and indent it, and Markdown will handle the hassle of encoding the\nampersands and angle brackets. For example, this:\n\n    <div class=\"footer\">\n        &copy; 2004 Foo Corporation\n    </div>\n\nRegular Markdown syntax is not processed within code blocks. E.g.,\nasterisks are just literal asterisks within a code block. This means\nit's also easy to use Markdown to write about Markdown's own syntax.\n\n```\ntell application \"Foo\"\n    beep\nend tell\n```\n\n## Span Elements\n\n### Links\n\nMarkdown supports two style of links: *inline* and *reference*.\n\nIn both styles, the link text is delimited by [square brackets].\n\nTo create an inline link, use a set of regular parentheses immediately\nafter the link text's closing square bracket. Inside the parentheses,\nput the URL where you want the link to point, along with an *optional*\ntitle for the link, surrounded in quotes. For example:\n\nThis is [an example](http://example.com/) inline link.\n\n[This link](http://example.net/) has no title attribute.\n\n### Emphasis\n\nMarkdown treats asterisks (`*`) and underscores (`_`) as indicators of\nemphasis. Text wrapped with one `*` or `_` will be wrapped with an\nHTML `<em>` tag; double `*`'s or `_`'s will be wrapped with an HTML\n`<strong>` tag. E.g., this input:\n\n*single asterisks*\n\n_single underscores_\n\n**double asterisks**\n\n__double underscores__\n\n### Code\n\nTo indicate a span of code, wrap it with backtick quotes (`` ` ``).\nUnlike a pre-formatted code block, a code span indicates code within a\nnormal paragraph. For example:\n\nUse the `printf()` function.\n";
+export declare const markdown = "\n# Markdown: Syntax\n\n*   [Overview](#overview)\n    *   [Philosophy](#philosophy)\n    *   [Inline HTML](#html)\n    *   [Automatic Escaping for Special Characters](#autoescape)\n*   [Block Elements](#block)\n    *   [Paragraphs and Line Breaks](#p)\n    *   [Headers](#header)\n    *   [Blockquotes](#blockquote)\n    *   [Lists](#list)\n    *   [Code Blocks](#precode)\n    *   [Horizontal Rules](#hr)\n*   [Span Elements](#span)\n    *   [Links](#link)\n    *   [Emphasis](#em)\n    *   [Code](#code)\n    *   [Images](#img)\n*   [Miscellaneous](#misc)\n    *   [Backslash Escapes](#backslash)\n    *   [Automatic Links](#autolink)\n\n\n----\n\n```sql\ndeclare @delete_user_cursor cursor\nset @delete_user_cursor = cursor for\nselect distinct A.USER_NAME, A.LOGIN_NAME from {db_super}.dbo.V_ACCESS_ACCOUNT_RIGHT A\n\tjoin {db_super}.dbo.V_ACCESS_ACCOUNT B on B.USER_NAME = A.USER_NAME and B.ORIGIN = 'helios'\n\tleft join #users C on C.LOGIN_NAME = A.LOGIN_NAME\n\twhere A.ID_ACCOUNTING_GROUP = @id_accounting_group and C.LOGIN_NAME is null\n\nopen @delete_user_cursor\n\tfetch next from @delete_user_cursor into @user_name, @login_name\n\twhile @@fetch_status = 0 begin\n\t\tbegin try\n\t\t\texec {db_super}.dbo.p_DELETE_USER @user_name, @who_created\n\t\t\tset @message = concat('delete user ', @login_name, ' (', @user_name, ')')\n\t\t\texec {db_super}.dbo.p_journal @id_audit, @id_call output, @accounting, @dr, 'users', 'p_DELETE_USER', 'P_ACCESS_ACCOUNT', 0, 1, @message, 1;\n\t\tend try begin catch\n\t\t\tset @message = concat(@login_name, ': ', error_message())\n\t\t\texec {db_super}.dbo.p_journal @id_audit, @id_call output, @accounting, @dr, 'users', 'p_DELETE_USER', 'P_ACCESS_ACCOUNT', 1, 0, @message, 1;\n\t\tend catch\n\t\t\t\t\t\t\t\t\t   \n\t\tfetch next from @delete_user_cursor into @user_name, @login_name\n\tend\nclose @delete_user_cursor   \ndeallocate @delete_user_cursor\n```\n\n\n## Overview\n\n### Philosophy\n\nMarkdown is intended to be as easy-to-read and easy-to-write as is feasible.\n\nReadability, however, is emphasized above all else. A Markdown-formatted\ndocument should be publishable as-is, as plain text, without looking\nlike it's been marked up with tags or formatting instructions. While\nMarkdown's syntax has been influenced by several existing text-to-HTML\nfilters -- including [Setext](http://docutils.sourceforge.net/mirror/setext.html), [atx](http://www.aaronsw.com/2002/atx/), [Textile](http://textism.com/tools/textile/), [reStructuredText](http://docutils.sourceforge.net/rst.html),\n[Grutatext](http://www.triptico.com/software/grutatxt.html), and [EtText](http://ettext.taint.org/doc/) -- the single biggest source of\ninspiration for Markdown's syntax is the format of plain text email.\n\n## Block Elements\n\n### Images\n![1.00](polar.jpeg \"Hello by a polar bear\")\n\n### Paragraphs and Line Breaks\n\nA paragraph is simply one or more consecutive lines of text, separated\nby one or more blank lines. (A blank line is any line that looks like a\nblank line -- a line containing nothing but spaces or tabs is considered\nblank.) Normal paragraphs should not be indented with spaces or tabs.\n\nThe implication of the \"one or more consecutive lines of text\" rule is\nthat Markdown supports \"hard-wrapped\" text paragraphs. This differs\nsignificantly from most other text-to-HTML formatters (including Movable\nType's \"Convert Line Breaks\" option) which translate every line break\ncharacter in a paragraph into a `<br />` tag.\n\nWhen you *do* want to insert a `<br />` break tag using Markdown, you\nend a line with two or more spaces, then type return.\n\n### Headers\n\nMarkdown supports two styles of headers, [Setext] [1] and [atx] [2].\n\nOptionally, you may \"close\" atx-style headers. This is purely\ncosmetic -- you can use this if you think it looks better. The\nclosing hashes don't even need to match the number of hashes\nused to open the header. (The number of opening hashes\ndetermines the header level.)\n\n\n### Blockquotes\n\nMarkdown uses email-style `>` characters for blockquoting. If you're\nfamiliar with quoting passages of text in an email message, then you\nknow how to create a blockquote in Markdown. It looks best if you hard\nwrap the text and put a `>` before every line:\n\n> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\n> consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\n> Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\n> \n> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\n> id sem consectetuer libero luctus adipiscing.\n\nMarkdown allows you to be lazy and only put the `>` before the first\nline of a hard-wrapped paragraph:\n\n> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\nconsectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\nVestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\n\n> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\nid sem consectetuer libero luctus adipiscing.\n\nBlockquotes can be nested (i.e. a blockquote-in-a-blockquote) by\nadding additional levels of `>`:\n\n> This is the first level of quoting.\n>\n> > This is nested blockquote.\n>\n> Back to the first level.\n\nBlockquotes can contain other Markdown elements, including headers, lists,\nand code blocks:\n\n> ## This is a header.\n> \n> 1.   This is the first list item.\n> 2.   This is the second list item.\n> \n> Here's some example code:\n> \n>     return shell_exec(\"echo $input | $markdown_script\");\n\nAny decent text editor should make email-style quoting easy. For\nexample, with BBEdit, you can make a selection and choose Increase\nQuote Level from the Text menu.\n\n\n### Lists\n\nMarkdown supports ordered (numbered) and unordered (bulleted) lists.\n\nUnordered lists use asterisks, pluses, and hyphens -- interchangably\n-- as list markers:\n\n*   Red\n*   Green\n*   Blue\n\nis equivalent to:\n\n+   Red\n+   Green\n+   Blue\n\nand:\n\n-   Red\n-   Green\n-   Blue\n\nOrdered lists use numbers followed by periods:\n\n1.  Bird\n2.  McHale\n3.  Parish\n\nIt's important to note that the actual numbers you use to mark the\nlist have no effect on the HTML output Markdown produces. The HTML\nMarkdown produces from the above list is:\n\nIf you instead wrote the list in Markdown like this:\n\n1.  Bird\n1.  McHale\n1.  Parish\n\nor even:\n\n3. Bird\n1. McHale\n8. Parish\n\nyou'd get the exact same HTML output. The point is, if you want to,\nyou can use ordinal numbers in your ordered Markdown lists, so that\nthe numbers in your source match the numbers in your published HTML.\nBut if you want to be lazy, you don't have to.\n\nTo make lists look nice, you can wrap items with hanging indents:\n\n*   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\n    Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\n    viverra nec, fringilla in, laoreet vitae, risus.\n*   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\n    Suspendisse id sem consectetuer libero luctus adipiscing.\n\nBut if you want to be lazy, you don't have to:\n\n*   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\nAliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\nviverra nec, fringilla in, laoreet vitae, risus.\n*   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\nSuspendisse id sem consectetuer libero luctus adipiscing.\n\nList items may consist of multiple paragraphs. Each subsequent\nparagraph in a list item must be indented by either 4 spaces\nor one tab:\n\n1.  This is a list item with two paragraphs. Lorem ipsum dolor\n    sit amet, consectetuer adipiscing elit. Aliquam hendrerit\n    mi posuere lectus.\n\n    Vestibulum enim wisi, viverra nec, fringilla in, laoreet\n    vitae, risus. Donec sit amet nisl. Aliquam semper ipsum\n    sit amet velit.\n\n2.  Suspendisse id sem consectetuer libero luctus adipiscing.\n\nIt looks nice if you indent every line of the subsequent\nparagraphs, but here again, Markdown will allow you to be\nlazy:\n\n*   This is a list item with two paragraphs.\n\n    This is the second paragraph in the list item. You're\nonly required to indent the first line. Lorem ipsum dolor\nsit amet, consectetuer adipiscing elit.\n\n*   Another item in the same list.\n\nTo put a blockquote within a list item, the blockquote's `>`\ndelimiters need to be indented:\n\n*   A list item with a blockquote:\n\n    > This is a blockquote\n    > inside a list item.\n\nTo put a code block within a list item, the code block needs\nto be indented *twice* -- 8 spaces or two tabs:\n\n*   A list item with a code block:\n\n        <code goes here>\n\n### Code Blocks\n\nPre-formatted code blocks are used for writing about programming or\nmarkup source code. Rather than forming normal paragraphs, the lines\nof a code block are interpreted literally. Markdown wraps a code block\nin both `<pre>` and `<code>` tags.\n\nTo produce a code block in Markdown, simply indent every line of the\nblock by at least 4 spaces or 1 tab.\n\nThis is a normal paragraph:\n\n    This is a code block.\n\nHere is an example of AppleScript:\n\n    tell application \"Foo\"\n        beep\n    end tell\n\nA code block continues until it reaches a line that is not indented\n(or the end of the article).\n\nWithin a code block, ampersands (`&`) and angle brackets (`<` and `>`)\nare automatically converted into HTML entities. This makes it very\neasy to include example HTML source code using Markdown -- just paste\nit and indent it, and Markdown will handle the hassle of encoding the\nampersands and angle brackets. For example, this:\n\n    <div class=\"footer\">\n        &copy; 2004 Foo Corporation\n    </div>\n\nRegular Markdown syntax is not processed within code blocks. E.g.,\nasterisks are just literal asterisks within a code block. This means\nit's also easy to use Markdown to write about Markdown's own syntax.\n\n```\ntell application \"Foo\"\n    beep\nend tell\n```\n\n## Span Elements\n\n### Links\n\nMarkdown supports two style of links: *inline* and *reference*.\n\nIn both styles, the link text is delimited by [square brackets].\n\nTo create an inline link, use a set of regular parentheses immediately\nafter the link text's closing square bracket. Inside the parentheses,\nput the URL where you want the link to point, along with an *optional*\ntitle for the link, surrounded in quotes. For example:\n\nThis is [an example](http://example.com/) inline link.\n\n[This link](http://example.net/) has no title attribute.\n\n### Emphasis\n\nMarkdown treats asterisks (`*`) and underscores (`_`) as indicators of\nemphasis. Text wrapped with one `*` or `_` will be wrapped with an\nHTML `<em>` tag; double `*`'s or `_`'s will be wrapped with an HTML\n`<strong>` tag. E.g., this input:\n\n*single asterisks*\n\n_single underscores_\n\n**double asterisks**\n\n__double underscores__\n\n### Code\n\nTo indicate a span of code, wrap it with backtick quotes (`` ` ``).\nUnlike a pre-formatted code block, a code span indicates code within a\nnormal paragraph. For example:\n\nUse the `printf()` function.\n";
 //# sourceMappingURL=markdown1.d.ts.map

package/dist/types/data/markdown1.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"markdown1.d.ts","sourceRoot":"","sources":["../../../src/data/markdown1.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,QAAQ,+5VAkVpB,CAAC"}
+{"version":3,"file":"markdown1.d.ts","sourceRoot":"","sources":["../../../src/data/markdown1.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,QAAQ,04VAkVpB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omegagrid/demo",
-  "version": "0.4.14",
+  "version": "0.4.15",
   "license": "UNLICENSED",
   "description": "Component showcase",
   "main": "./dist/index.js",
@@ -40,22 +40,22 @@
     "@fortawesome/fontawesome-svg-core": "6.4.2",
     "@fortawesome/pro-light-svg-icons": "6.4.2",
     "@fortawesome/pro-solid-svg-icons": "6.4.2",
-    "@omegagrid/bucket": "^0.4.14",
-    "@omegagrid/code": "^0.4.14",
-    "@omegagrid/commands": "^0.4.14",
-    "@omegagrid/core": "^0.4.14",
-    "@omegagrid/dialog": "^0.4.14",
-    "@omegagrid/editor": "^0.4.14",
-    "@omegagrid/form": "^0.4.14",
-    "@omegagrid/grid": "^0.4.14",
-    "@omegagrid/localize": "^0.4.14",
-    "@omegagrid/markdown": "^0.4.14",
-    "@omegagrid/plugin-charts": "^0.4.14",
-    "@omegagrid/plugin-xlsx": "^0.4.14",
-    "@omegagrid/statusbar": "^0.4.14",
-    "@omegagrid/tabs": "^0.4.14",
-    "@omegagrid/toolbar": "^0.4.14",
-    "@omegagrid/tree": "^0.4.14",
+    "@omegagrid/bucket": "^0.4.15",
+    "@omegagrid/code": "^0.4.15",
+    "@omegagrid/commands": "^0.4.15",
+    "@omegagrid/core": "^0.4.15",
+    "@omegagrid/dialog": "^0.4.15",
+    "@omegagrid/editor": "^0.4.15",
+    "@omegagrid/form": "^0.4.15",
+    "@omegagrid/grid": "^0.4.15",
+    "@omegagrid/localize": "^0.4.15",
+    "@omegagrid/markdown": "^0.4.15",
+    "@omegagrid/plugin-charts": "^0.4.15",
+    "@omegagrid/plugin-xlsx": "^0.4.15",
+    "@omegagrid/statusbar": "^0.4.15",
+    "@omegagrid/tabs": "^0.4.15",
+    "@omegagrid/toolbar": "^0.4.15",
+    "@omegagrid/tree": "^0.4.15",
     "@reporting/rp-utils-csv": "^1.0.0",
     "@sheet/core": "^1",
     "lit": "^3.1.1",