zed/crates/time_format/Cargo.toml

[package]
name = "time_format"
version = "0.1.0"
edition.workspace = true
publish.workspace = true
license = "GPL-3.0-or-later"

[lints]
workspace = true

[lib]
path = "src/time_format.rs"
doctest = false

[dependencies]
sys-locale.workspace = true
time.workspace = true

[target.'cfg(target_os = "macos")'.dependencies]
core-foundation.workspace = true
core-foundation-sys.workspace = true
Respect user preferences when formatting timestamp (#7994) This is a follow up to #7945. The current behaviour reads the locale and infers from that which type of time format should be used (12 hour/24 hour). However, in macOS you can override this behaviour, e.g. you can use en_US locale but still use the 24 hour clock format (Can be customized under Settings > General > Date & Format > 24-hour time). You can even customize the date format. This PR uses the macOS specific `CFDateFormatter` API, which outputs time format strings, that respect those settings. Partially fixes #7956 (as its not implemented for linux) Release Notes: - Added localization support for all macOS specific date and time configurations in chat 2024-02-24 02:18:06 +00:00			`[package]`
			`name = "time_format"`
			`version = "0.1.0"`
chore: Use workspace fields for edition and publish (#23291) This prepares us for an upcoming bump to Rust 2024 edition. Release Notes: - N/A 2025-01-17 16:39:22 +00:00			`edition.workspace = true`
			`publish.workspace = true`
Respect user preferences when formatting timestamp (#7994) This is a follow up to #7945. The current behaviour reads the locale and infers from that which type of time format should be used (12 hour/24 hour). However, in macOS you can override this behaviour, e.g. you can use en_US locale but still use the 24 hour clock format (Can be customized under Settings > General > Date & Format > 24-hour time). You can even customize the date format. This PR uses the macOS specific `CFDateFormatter` API, which outputs time format strings, that respect those settings. Partially fixes #7956 (as its not implemented for linux) Release Notes: - Added localization support for all macOS specific date and time configurations in chat 2024-02-24 02:18:06 +00:00			`license = "GPL-3.0-or-later"`

Move Clippy configuration to the workspace level (#8891) This PR moves the Clippy configuration up to the workspace level. We're using the [`lints` table](https://doc.rust-lang.org/cargo/reference/workspaces.html#the-lints-table) to configure the Clippy ruleset in the workspace's `Cargo.toml`. Each crate in the workspace now has the following in their own `Cargo.toml` to inherit the lints from the workspace: ```toml [lints] workspace = true ``` This allows for configuring rust-analyzer to show Clippy lints in the editor by using the following configuration in your Zed `settings.json`: ```json { "lsp": { "rust-analyzer": { "initialization_options": { "check": { "command": "clippy" } } } } ``` Release Notes: - N/A 2024-03-05 17:01:17 +00:00			`[lints]`
			`workspace = true`

Respect user preferences when formatting timestamp (#7994) This is a follow up to #7945. The current behaviour reads the locale and infers from that which type of time format should be used (12 hour/24 hour). However, in macOS you can override this behaviour, e.g. you can use en_US locale but still use the 24 hour clock format (Can be customized under Settings > General > Date & Format > 24-hour time). You can even customize the date format. This PR uses the macOS specific `CFDateFormatter` API, which outputs time format strings, that respect those settings. Partially fixes #7956 (as its not implemented for linux) Release Notes: - Added localization support for all macOS specific date and time configurations in chat 2024-02-24 02:18:06 +00:00			`[lib]`
			`path = "src/time_format.rs"`
			`doctest = false`

			`[dependencies]`
			`sys-locale.workspace = true`
			`time.workspace = true`

			`[target.'cfg(target_os = "macos")'.dependencies]`
			`core-foundation.workspace = true`
			`core-foundation-sys.workspace = true`