mirror of
https://github.com/rust-lang/rust-analyzer.git
synced 2025-09-28 04:44:57 +00:00
Tease apart orthogonal concerns in markdown link rewriting
`hir` should know nothing about URLs, markdown and html. It should only be able to: * resolve stringy path from documentation * generate canonical stringy path for a def In contrast, link rewriting should not care about semantics of paths and names resolution, and should be concern only with text mangling bits.
This commit is contained in:
parent
3d6c4c143b
commit
f8a59adf5e
9 changed files with 297 additions and 337 deletions
|
@ -27,19 +27,17 @@ pub mod diagnostics;
|
|||
|
||||
mod from_id;
|
||||
mod code_model;
|
||||
mod doc_links;
|
||||
mod attrs;
|
||||
mod has_source;
|
||||
|
||||
pub use crate::{
|
||||
attrs::HasAttrs,
|
||||
attrs::{HasAttrs, Namespace},
|
||||
code_model::{
|
||||
Access, Adt, AsAssocItem, AssocItem, AssocItemContainer, Callable, CallableKind, Const,
|
||||
Crate, CrateDependency, DefWithBody, Enum, EnumVariant, Field, FieldSource, Function,
|
||||
GenericDef, HasVisibility, ImplDef, Local, MacroDef, Module, ModuleDef, ScopeDef, Static,
|
||||
Struct, Trait, Type, TypeAlias, TypeParam, Union, VariantDef, Visibility,
|
||||
},
|
||||
doc_links::resolve_doc_link,
|
||||
has_source::HasSource,
|
||||
semantics::{original_range, PathResolution, Semantics, SemanticsScope},
|
||||
};
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue