Skip to content

Re-export regress to avoid a peer dependency#1009

Open
jeffs wants to merge 1 commit intooxidecomputer:mainfrom
jeffs:reexport-regress
Open

Re-export regress to avoid a peer dependency#1009
jeffs wants to merge 1 commit intooxidecomputer:mainfrom
jeffs:reexport-regress

Conversation

@jeffs
Copy link
Copy Markdown

@jeffs jeffs commented May 10, 2026

The import_types! macro currently emits validation code that references ::regress::Regex, forcing every macro consumer to declare regress as a direct dependency. This commit re-exports regress from typify under a #[doc(hidden)] alias, and routes the macro's emitted path through ::typify::regress, so callers can drop the regress entry from Cargo.toml.

The default emitted path remains ::regress, so cargo-typify, build.rs users, and direct typify-impl callers are unaffected. A new TypeSpaceSettings::with_regress_crate setter exposes the override.

The import_types! macro emits validation code that referenced
::regress::Regex, forcing every macro consumer to declare regress
as a direct dependency. This commit re-exports regress from typify
under a #[doc(hidden)] alias, and routes the macro's emitted path
through ::typify::regress, so callers can drop the regress entry from
Cargo.toml.

The default emitted path remains ::regress, so cargo-typify,
build.rs users, and direct typify-impl callers are unaffected. A new
TypeSpaceSettings::with_regress_crate setter exposes the override.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant