Fix outdated links
This commit is contained in:
parent
7412664c26
commit
8b9e20b842
@ -1,8 +1,10 @@
|
||||
# ruma-api-macros
|
||||
|
||||
**ruma-api-macros** provides a procedural macro for easily generating [ruma-api](https://github.com/ruma/ruma-api)-compatible API endpoints.
|
||||
**ruma-api-macros** provides a procedural macro for easily generating [ruma-api]-compatible API endpoints.
|
||||
You define the endpoint's metadata, request fields, and response fields, and the macro generates all the necessary types and implements all the necessary traits.
|
||||
|
||||
[ruma-api]: https://github.com/ruma/ruma/tree/master/ruma-api
|
||||
|
||||
## Usage
|
||||
|
||||
This crate is not meant to be used directly; instead, you can use it through the re-exports in ruma-api.
|
||||
|
@ -1,9 +1,11 @@
|
||||
//! Crate ruma-api-macros provides a procedural macro for easily generating
|
||||
//! [ruma-api](https://github.com/ruma/ruma-api)-compatible endpoints.
|
||||
//! [ruma-api]-compatible endpoints.
|
||||
//!
|
||||
//! This crate should never be used directly; instead, use it through the
|
||||
//! re-exports in ruma-api. Also note that for technical reasons, the
|
||||
//! `ruma_api!` macro is only documented in ruma-api, not here.
|
||||
//!
|
||||
//! [ruma-api]: https://github.com/ruma/ruma/tree/master/ruma-api
|
||||
|
||||
#![allow(clippy::cognitive_complexity)]
|
||||
// Remove this once https://github.com/rust-lang/rust/issues/54883 becomes stable
|
||||
|
@ -181,7 +181,9 @@ Breaking changes:
|
||||
|
||||
Breaking changes:
|
||||
|
||||
The crate has been redesign to focus on conversions between an endpoint's request and response types and Hyper request and response types. Implementations are expected to be generated via [ruma-api-macros](https://github.com/ruma/ruma-api-macros).
|
||||
The crate has been redesign to focus on conversions between an endpoint's request and response types and Hyper request and response types. Implementations are expected to be generated via [ruma-api-macros].
|
||||
|
||||
[ruma-api-macros]: https://github.com/ruma/ruma/tree/master/ruma-api-macros
|
||||
|
||||
# 0.3.0
|
||||
|
||||
|
@ -7,12 +7,12 @@ categories = ["api-bindings", "web-programming"]
|
||||
description = "A Matrix client library."
|
||||
documentation = "https://docs.rs/ruma-client"
|
||||
edition = "2018"
|
||||
homepage = "https://github.com/ruma/ruma-client"
|
||||
homepage = "https://www.ruma.io/"
|
||||
keywords = ["matrix", "chat", "messaging", "ruma"]
|
||||
license = "MIT"
|
||||
name = "ruma-client"
|
||||
readme = "README.md"
|
||||
repository = "https://github.com/ruma/ruma-client"
|
||||
repository = "https://github.com/ruma/ruma"
|
||||
version = "0.4.0"
|
||||
|
||||
[dependencies]
|
||||
|
@ -1,6 +1,8 @@
|
||||
# ruma-events-macros
|
||||
|
||||
**ruma-events-macros** provides a procedural macro for easily generating event types for [ruma-events](https://github.com/ruma/ruma-events).
|
||||
**ruma-events-macros** provides a procedural macro for easily generating event types for [ruma-events].
|
||||
|
||||
[ruma-events]: https://github.com/ruma/ruma/tree/master/ruma-events
|
||||
|
||||
## Documentation
|
||||
|
||||
|
@ -1,7 +1,9 @@
|
||||
//! Crate `ruma_events_macros` provides a procedural macro for generating
|
||||
//! [ruma-events](https://github.com/ruma/ruma-events) events.
|
||||
//! [ruma-events] events.
|
||||
//!
|
||||
//! See the documentation for the individual macros for usage details.
|
||||
//!
|
||||
//! [ruma-events]: https://github.com/ruma/ruma/tree/master/ruma-events
|
||||
|
||||
#![deny(missing_copy_implementations, missing_debug_implementations, missing_docs)]
|
||||
|
||||
|
@ -57,7 +57,7 @@ Breaking changes:
|
||||
exceeding 32 code points in length). Use the `TryFrom<&str>` or `TryFrom<String>` implementation
|
||||
instead.
|
||||
* Remove diesel integration. If you were using it, please comment on the corresponding issue:
|
||||
https://github.com/ruma/ruma-identifiers/issues/22
|
||||
[#22](https://github.com/ruma/ruma-identifiers/issues/22)
|
||||
* Remove `TryFrom<Cow<'_, str>>` implementations for identifier types
|
||||
* Update `parse_with_server_name`s signature (instead of `Into<String>` it now requires
|
||||
`Into<Box<str>>` of the id type). This is technically a breaking change, but extremely unlikely
|
||||
|
Loading…
x
Reference in New Issue
Block a user