Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 17:41
    renovate[bot] synchronize #1105
  • 17:41

    renovate[bot] on safe

    chore(deps): update safe (compare)

  • 17:36

    renovate[bot] on configure

    (compare)

  • 17:36
    renovate[bot] closed #1103
  • 17:36
    renovate[bot] edited #1103
  • 17:36
    renovate[bot] opened #1110
  • 17:36

    renovate[bot] on swatinem-rust-cache-2.x

    chore(deps): update swatinem/ru… (compare)

  • 17:36
    renovate[bot] opened #1109
  • 17:36

    renovate[bot] on html-minifier-4.x

    chore(deps): update rust crate … (compare)

  • 17:33

    epage on actions-upload-release-asset-1.x

    (compare)

  • 17:33

    epage on master

    chore(deps): update actions/upl… Merge pull request #1104 from c… (compare)

  • 17:33
    epage closed #1104
  • 17:31
    renovate[bot] opened #1108
  • 17:31

    renovate[bot] on actions-checkout-3.x

    chore(deps): update actions/che… (compare)

  • 17:31
    renovate[bot] opened #1107
  • 17:31

    renovate[bot] on regex-1.x

    chore(deps): update rust crate … (compare)

  • 17:23
    renovate[bot] opened #1106
  • 17:23

    renovate[bot] on env_logger-0.x

    chore(deps): update rust crate … (compare)

  • 17:18
    renovate[bot] opened #1105
  • 17:18

    renovate[bot] on safe

    chore(deps): update safe (compare)

Ed Page
@epage
Just hadn't gotten to it yet
Done
David J. Weller-Fahy
@djwf
Thanks - is there anything that I should look at next?
Or just start with the oldest things and go from there?
Ed Page
@epage
The things pressing on my mind the most for liquid are
  • Adding the newest style of include and making sure all three are compliant
  • Updating the conformance tests
  • Experimenting with a nom based parser that provides a toolbox of parser that can be split out into its own crate with indepndent versioning, kind of like how regex has regex_syntax. To reduce exposing too much implementation details, the current parser API is fairly rigid
David J. Weller-Fahy
@djwf
Got it - I'll poke around a bit, thanks!
David J. Weller-Fahy
@djwf
so the goal of the nom parser would be to have a crate syntax that would contain the sum total of the syntax parsing, and could be used by other crates within our project, correct?
Ed Page
@epage
It can't provide a complete top-level syntax because the grammar is pluggable but it should allow for incremental parsing. This would then be used by blocks and tags to parse their their arguments and content. Its broken out so we can freely change i without breaking the rest of the API, like regex_syntax
I also find pest slow to compile and unergonomic to work with
David J. Weller-Fahy
@djwf
Makes sense - I like the combinator method better than an overarching parser. I'll start stubbing it out, and will probably bug you about overall design after I get a feel for it.
Jaafar
@jaafar:kde.org
[m]
Is there any way to do i18n/L10n in Cobalt or is that not supported right now?
Ed Page
@epage
There is not. cobalt-org/cobalt.rs#392 is the issue for it
Jaafar
@jaafar:kde.org
[m]

Yeah, I saw that. I just asked the question out of a false sense of hope as if there's another way to do it. :(

Moving to Zola is an option, but its huge distinction between sections/pages is kinda messing me up and forcing me to completely rethink everything from scratch. I'll see what I can do.

If this is the end for me and Cobalt, then it's been fun, and I thoroughly enjoyed the software. I salute and appreciate the developers and their amazing efforts. Sorry if I sound oddly dramatic here, but I really mean it. :)

SArpnt
@SArpnt
cobalt says it has support for sass but that assets get mirrored directly
is sass minified but not css?
Ed Page
@epage
iirc all CSS should be minified, both assets and sass
The comment about assets probably hasn't been updated since minification was added
SArpnt
@SArpnt
if that's the case then i'm pretty sure the documentation isn't right https://cobalt-org.github.io/docs/assets/
it says css is a non page asset and that non page assets are unchanged
FantasyCookie17 🏳️‍🌈🏳️‍⚧️
@fantasycookie17:artemislena.eu
[m]
Minification… was added? When?
Ed Page
@epage
SArpnt
@SArpnt
i'm trying to use cobalt serve but i'm getting absolutely nothing in the browser, there's no difference from when there's no server running
to be clear i'm on the url and port it says in the console output
Tassilo Horn
@tsdh
Which markdown variant does cobalt use? (I want to see if/how I can somehow scale images.)
Ed Page
@epage
cobalt is using the pulldown-cmark parser. See https://crates.io/crates/pulldown-cmark for details on what it supports
Tassilo Horn
@tsdh
epage: Thanks!
SArpnt
@SArpnt
tried on a completely different computer with a fresh cobalt init and serve still doesn't work
after doing a debug log it shows [::1]:3000 instead of the http://localhost:3000 shown by the info log
the server is only running on ipv6?
Ed Page
@epage
@SArpnt I'm sorry, I somehow missed your previous message about this. Thanks for the further details. Could you open an issue about that so it'll be easier to track?
Almaz Murzabekov
@almazmurzabekov_gitlab

Hey there!

Sorry for dummy question, but how can I format published_date value? Instead of having YYYY-MM-DD HH:MM:SS TZ I want to see YYYY-MM-DD HH:MM

FantasyCookie17 🏳️‍🌈🏳️‍⚧️
@fantasycookie17:artemislena.eu
[m]
Though… don't even know… if that… works with Cobalt's date format… if not… try https://shopify.github.io/liquid/filters/split/
FantasyCookie17 🏳️‍🌈🏳️‍⚧️
@fantasycookie17:artemislena.eu
[m]
Also… {{page.published_date | replace: " +", "+" | replace: " -", "-"}} is… what we use to get ISO time… for… the datetime attribute of <time>
Almaz Murzabekov
@almazmurzabekov_gitlab
Thank you @fantasycookie17:artemislena.eu, {{ page.published_date | date: "%Y-%m-%d %H:%M" }} works for me !
FantasyCookie17 🏳️‍🌈🏳️‍⚧️
@fantasycookie17:artemislena.eu
[m]
💖