OpenSourceArk/obsidian-export
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
e197ac3408
obsidian-export/Cargo.toml

49 lines
1.1 KiB
TOML
Raw Normal View History

Public release
2020-11-28 15:14:50 +03:00
[package]
name = "obsidian-export"
Release v22.11.0
2022-11-19 19:09:43 +03:00
version = "22.11.0"
Public release
2020-11-28 15:14:50 +03:00
authors = ["Nick Groenen <nick@groenen.me>"]
edition = "2018"
license = "MIT OR Apache-2.0"
readme = "README.md"
repository = "https://github.com/zoni/obsidian-export"
documentation = "https://docs.rs/obsidian-export"
description = """
Rust library and associated CLI program to export an Obsidian vault to regular Markdown.
"""
categories = ["command-line-utilities", "text-processing"]
keywords = ["markdown", "obsidian"]
[lib]
name = "obsidian_export"
path = "src/lib.rs"
[[bin]]
name = "obsidian-export"
path = "src/main.rs"
Don't build docs for the bin target The library contains documentation covering both CLI and library usage, there's no separate documentation for just the binary target.
2021-09-12 15:42:07 +03:00
doc = false
Public release
2020-11-28 15:14:50 +03:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
Upgrade minor dependencies
2022-11-05 16:20:24 +03:00
eyre = "0.6.8"
gumdrop = "0.8.1"
Upgrade dependencies This commit upgrades all dependencies to their current latest versions. Most notably, this includes upgrades to the following most critical libraries: pulldown-cmark v0.8.0 -> v0.9.0 pulldown-cmark-to-cmark v7.1.1 -> v9.0.0 In total, these dependencies were upgraded: bstr v0.2.16 -> v0.2.17 ignore v0.4.17 -> v0.4.18 libc v0.2.101 -> v0.2.112 memoffset v0.6.4 -> v0.6.5 num_cpus v1.13.0 -> v1.13.1 once_cell v1.8.0 -> v1.9.0 ppv-lite86 v0.2.10 -> v0.2.16 proc-macro2 v1.0.29 -> v1.0.36 pulldown-cmark v0.8.0 -> v0.9.0 pulldown-cmark-to-cmark v7.1.1 -> v9.0.0 quote v1.0.9 -> v1.0.14 rayon v1.5.0 -> v1.5.1 regex v1.5.3 -> v1.5.4 serde v1.0.130 -> v1.0.132 syn v1.0.75 -> v1.0.84 unicode-width v0.1.8 -> v0.1.9 version_check v0.9.3 -> v0.9.4
2022-01-02 01:34:46 +03:00
ignore = "0.4.18"
Public release
2020-11-28 15:14:50 +03:00
lazy_static = "1.4.0"
matter = "0.1.0-alpha4"
Bump pathdiff from 0.2.0 to 0.2.1 (#46) Bumps [pathdiff](https://github.com/Manishearth/pathdiff) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/Manishearth/pathdiff/releases) - [Commits](https://github.com/Manishearth/pathdiff/commits) --- updated-dependencies: - dependency-name: pathdiff dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2021-10-06 20:38:25 +03:00
pathdiff = "0.2.1"
Bump percent-encoding from 2.2.0 to 2.3.0 (#171)
2023-09-22 12:32:25 +03:00
percent-encoding = "2.3.0"
Upgrade minor dependencies
2022-11-05 16:20:24 +03:00
pulldown-cmark = "0.9.2"
Bump pulldown-cmark-to-cmark from 10.0.4 to 11.0.0 (#168)
2023-09-22 12:42:21 +03:00
pulldown-cmark-to-cmark = "11.0.0"
Bump rayon from 1.5.3 to 1.6.0 (#134) Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.5.3 to 1.6.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/v1.5.3...rayon-core-v1.6.0) --- updated-dependencies: - dependency-name: rayon dependency-type: direct:production 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>
2022-11-29 12:54:28 +03:00
rayon = "1.6.0"
Bump regex from 1.7.0 to 1.9.4 (#170)
2023-09-22 12:32:44 +03:00
regex = "1.9.4"
Bump serde_yaml from 0.9.14 to 0.9.25 (#167)
2023-09-22 12:39:01 +03:00
serde_yaml = "0.9.25"
new: support links referencing headings Previously, links referencing a heading (`[[note#heading]]`) would just link to the file name without including an anchor in the link target. Now, such references will include an appropriate `#anchor` attribute. Note that neither the original Markdown specification, nor the more recent CommonMark standard, specify how anchors should be constructed for a given heading. There are also some differences between the various Markdown rendering implementations. Obsidian-export uses the [slug] crate to generate anchors which should be compatible with most implementations, however your mileage may vary. (For example, GitHub may leave a trailing `-` on anchors when headings end with a smiley. The slug library, and thus obsidian-export, will avoid such dangling dashes). [slug]: https://crates.io/crates/slug
2021-01-04 23:17:46 +03:00
slug = "0.1.4"
Bump snafu from 0.7.3 to 0.7.5 (#164)
2023-09-22 12:43:30 +03:00
snafu = "0.7.5"
New: apply unicode normalization while resolving notes The unicode standard allows for certain (visually) identical characters to be represented in different ways. For example the character ä may be represented as a single combined codepoint "Latin Small Letter A with Diaeresis" (U+00E4) or by the combination of "Latin Small Letter A" (U+0061) followed by "Combining Diaeresis" (U+0308). When encoded with UTF-8, these are represented as respectively the two bytes 0xC3 0xA4, and the three bytes 0x61 0xCC 0x88. A user linking to notes with these characters in their titles would expect these two variants to link to the same file, given they are visually identical and have the exact same semantic meaning. The unicode standard defines a method to deconstruct and normalize these forms, so that a byte comparison on the normalized forms of these variants ends up comparing the same thing. This is called Unicode Normalization, defined in Unicode® Standard Annex #15 (http://www.unicode.org/reports/tr15/). The W3C Working Group has written an excellent explanation of the problems regarding string matching, and how unicode normalization helps with this process: https://www.w3.org/TR/charmod-norm/#unicodeNormalization With this change, obsidian-export will perform unicode normalization (specifically the C (or NFC) normalization form) on all note titles while looking up link references, ensuring visually identical links are treated as being similar, even if they were encoded as different variants. A special thanks to Hans Raaf (@oderwat) for reporting and helping track down this issue. --- Closes #126
2022-11-19 18:34:17 +03:00
unicode-normalization = "0.1.22"
Public release
2020-11-28 15:14:50 +03:00
[dev-dependencies]
Bump pretty_assertions from 1.3.0 to 1.4.0 (#169)
2023-09-22 12:31:11 +03:00
pretty_assertions = "1.4.0"
Bump rstest from 0.16.0 to 0.17.0 (#166)
2023-09-22 12:35:03 +03:00
rstest = "0.17.0"
Bump tempfile from 3.3.0 to 3.8.0 (#172)
2023-09-22 12:43:56 +03:00
tempfile = "3.8.0"
Bump walkdir from 2.3.1 to 2.3.2 Bumps [walkdir](https://github.com/BurntSushi/walkdir) from 2.3.1 to 2.3.2. - [Release notes](https://github.com/BurntSushi/walkdir/releases) - [Commits](https://github.com/BurntSushi/walkdir/compare/2.3.1...2.3.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-29 09:26:37 +03:00
walkdir = "2.3.2"
Reference in New Issue Copy Permalink