UziTech
Repos
415
Followers
80
Following
2

A markdown parser and compiler. Built for speed.

28358
3033

An Atom.io package to use git from the context menu

14
5

A test runner for Atom using Jasmine 3.x

Generate, play and solve sudoku puzzles

1
0

GitHub action to setup Atom and APM

27
13

Lint your CoffeeScript.

12
10

Events

issue comment
custom pipeline

@scruel I moved the question to a new issue so we don't take over the other thread.

The marked lexer works by consuming tokens in the beginning of the source. I think what you are proposing would require rewriting the lexer and parser.

Created at 9 hours ago
opened issue
custom pipeline
    > Right now though I'm unsure which `raw` components we'd even want to add up though... because it's not as simple as "ignore the parent, always add up the children" or anything (at a glance), say taking the example:
> require('marked').lexer('> I am using marked.')
[
  {
    type: "blockquote",
    raw: "> I am using marked.",
    tokens: [
      {
        type: "paragraph",
        raw: "I am using marked.",
        text: "I am using marked.",
        tokens: [
          {
            type: "text",
            raw: "I am using marked.",
            text: "I am using marked."
          }
        ]
      }
    ]
  },
  links: {}
]

The same content "I am using marked." is repeated 3 times in raw... and the top-most node also includes the prefix "> " for the block quote... we'd need to know that block quote started at index 0 and that paragraph started at position 2 (or 3, etc, it would depend in the whitespace I imagine)...

I mean I suppose we could try to write handlers for each type of token on our side... so that we analyze the >... prefix ourselves, then increment the index accordingly before we jump into the children... I think I was hoping it might be easier than that... the big benefit would be if we could leverage marked with just some very simple glue code. As soon as we have to build a whole in-between analyzer... the benefits start to disappear fast.

Might be time to dig into the lexer source and poke around.

It's really a problem, and I have no idea how to put the lex result back to content, what I am focusing on will only be the parts which are not code, rather than get a result of everything. Even lex can result all information we needed to handle the content, to get the certain part of content, I have to execute the render for many times, it definitely will affect the rendering performance and slow the site.

@UziTech Is there any way we can custom the pipeline like step-by-step process the content? The best will be that we can even custom the jobs order in pipeline:

```code```\n\n<!-- commnents --> here\n\n```<!-- commnents -->```\n# <!-- commnents --> in heading `code`\n
marked(content, [
'code',
'custom1',
'heading',
'custom2',
]);
  1. Code step(Should only use code rules to handling content):
<pre><code>code</pre></code>\n\n<!-- commnents --> here\n\n<pre></code><!-- commnents --><pre></code>\n# <!-- commnents --> in heading <code>code</code>\n
  1. custom parser – Comment Replacer (can use Marked's render or render content as you wish)
// Replace '<!-- custom commnents -->' into 'text'(ignore the code block):
<pre><code>code</pre></code>\n\ntext here\n\n<pre></code><!-- commnents --><pre></code>\n# text in heading <code>code</code>\n
  1. heading step
<pre><code>code</pre></code>\n\ntext here\n\n<pre></code><!-- commnents --><pre></code>\n<h1>text in heading <code>code</code></h1>\n
  1. custom parser – Add links to heading
<pre><code>code</pre></code>\n\ntext here\n\n<pre></code><!-- commnents --><pre></code>\n<h1 href='#text-1024'>text in heading <code>code</code></h1>\n
  1. return result

I don't think I need to open a new issue for what I said about, if you pefer me to do that, let me know.

Originally posted by @scruel in https://github.com/markedjs/marked/issues/2443#issuecomment-1259037699

Created at 9 hours ago

fix(deps): update dependency sequelize to ^6.23.2

Merge pull request #490 from UziTech/renovate/sequelize-6.x

fix(deps): update dependency sequelize to ^6.23.2

Created at 1 day ago
pull request closed
fix(deps): update dependency sequelize to ^6.23.2

Mend Renovate

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | sequelize (source) | ^6.23.0 -> ^6.23.2 | age | adoption | passing | confidence |


Release Notes

v6.23.2

Compare Source

Bug Fixes
  • postgres: add custom order direction to subQuery ordering with minified alias (#​15056) (7203b66)

v6.23.1

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

Created at 1 day ago
pull request closed
chore(deps-dev): Bump eslint from 8.23.1 to 8.24.0

Bumps eslint from 8.23.1 to 8.24.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 2 days ago
delete branch
UziTech delete branch dependabot/npm_and_yarn/eslint-8.24.0
Created at 2 days ago

chore(deps-dev): Bump eslint from 8.23.1 to 8.24.0 (#189)

Bumps eslint from 8.23.1 to 8.24.0.


updated-dependencies:

  • dependency-name: eslint dependency-type: direct:development update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Created at 2 days ago

chore(deps-dev): Bump uglify-js from 3.17.0 to 3.17.2 (#2590)

Bumps uglify-js from 3.17.0 to 3.17.2.


updated-dependencies:

  • dependency-name: uglify-js dependency-type: direct:development update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Created at 2 days ago
delete branch
UziTech delete branch dependabot/npm_and_yarn/uglify-js-3.17.2
Created at 2 days ago
pull request closed
chore(deps-dev): Bump uglify-js from 3.17.0 to 3.17.2

Bumps uglify-js from 3.17.0 to 3.17.2.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 2 days ago

chore(deps-dev): Bump rollup from 2.79.0 to 2.79.1 (#2591)

Bumps rollup from 2.79.0 to 2.79.1.


updated-dependencies:

  • dependency-name: rollup dependency-type: direct:development update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Created at 2 days ago
delete branch
UziTech delete branch dependabot/npm_and_yarn/rollup-2.79.1
Created at 2 days ago
pull request closed
chore(deps-dev): Bump rollup from 2.79.0 to 2.79.1

Bumps rollup from 2.79.0 to 2.79.1.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 2 days ago

chore(deps-dev): Bump eslint from 8.23.1 to 8.24.0 (#2592)

Bumps eslint from 8.23.1 to 8.24.0.


updated-dependencies:

  • dependency-name: eslint dependency-type: direct:development update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Created at 2 days ago
delete branch
UziTech delete branch dependabot/npm_and_yarn/eslint-8.24.0
Created at 2 days ago
pull request closed
chore(deps-dev): Bump eslint from 8.23.1 to 8.24.0

Bumps eslint from 8.23.1 to 8.24.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 2 days ago
pull request closed
chore(deps-dev): Bump eslint-plugin-n from 15.2.5 to 15.3.0

Bumps eslint-plugin-n from 15.2.5 to 15.3.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 2 days ago
delete branch
UziTech delete branch dependabot/npm_and_yarn/eslint-plugin-n-15.3.0
Created at 2 days ago

chore(deps-dev): Bump eslint-plugin-n from 15.2.5 to 15.3.0 (#2593)

Bumps eslint-plugin-n from 15.2.5 to 15.3.0.


updated-dependencies:

  • dependency-name: eslint-plugin-n dependency-type: direct:development update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Created at 2 days ago
delete branch
UziTech delete branch change-width-button
Created at 5 days ago

docs: add change width button (#658)

Created at 5 days ago
pull request closed
docs: add change width button
Created at 5 days ago
pull request opened
docs: add change width button
Created at 5 days ago

docs: add change width button

Created at 5 days ago
create branch
UziTech create branch change-width-button
Created at 5 days ago

fix: use point group options in calculations

fix: add velocityFilterWeight to point group options

test: test fromData with options change

Merge pull request #657 from UziTech/point-group-options

Created at 5 days ago
delete branch
UziTech delete branch point-group-options
Created at 5 days ago
closed issue
line width not restored

Seems to be a bug in version 4.0.8

line width is not correctly drawn when using fromData(data)

We are using 4 different line widths (using minWidth and maxWidth) to draw lines (the user can select a line width):

  1. thinner than default (0.4, 1)
  2. default (0.5, 2.5)
      1. thicker than default. (1, 5 and 5, 10)

Steps to reproduce?

  1. Draw 4 lines with different line width (see above)
  2. save the point data using toData()
  3. load the data with fromData() --> the line width is not correct. All lines with a thicker width than default are now in default line width (although the correct information is in the point data). Only the thinner ones are correct.

Images: 2022-09-23 12_34_49-Window --> after fromData(): 2022-09-23 12_35_01-Window

What is the expected behavior? Redraw the correct line width after loading data with fromData()

**Additional Information ** Seems that all lines which are thicker than default will be drawn in the default line width. Setting the line width before loading data with fromData() to the highest line width will draw all lines correctly.

Created at 5 days ago
pull request closed
fix: use point group options in calculations

fixes #656

Created at 5 days ago
pull request opened
fix: use point group options in calculations

fixes #656

Created at 5 days ago