Feature Request: Expose the package name #17

New Issue

2026-03-12T15:08:06Z

zral0kh commented

2026-03-12 15:08:06 +00:00

First thanks for making this really compatible with cetz (only a shallow wrapper), that makes so many things easier.

I want to integrate all cetz-based drawing packages with touying nicely, which requires conditionally accessing packages, which only really works by having the user input the module and us recognizing it.

Thus i need to recognize packages, which currently is hard to do, so please expose the module name.
at best just as #let name = circuiteria in your lib.typ

thx

First thanks for making this really compatible with cetz (only a shallow wrapper), that makes so many things easier. I want to integrate all cetz-based drawing packages with touying nicely, which requires conditionally accessing packages, which only really works by having the user input the module and us recognizing it. Thus i need to recognize packages, which currently is hard to do, so please expose the module name. at best just as `#let name = circuiteria` in your `lib.typ` thx

HEL commented

2026-03-12 17:31:38 +00:00

Thank you for taking interest in Circuiteria

I'm not sure I understand the need for a package to expose its name. What do you mean by "conditionally accessing packages" ?
Wouldn't users simply import the package and use it directly in their document ?

Thank you for taking interest in Circuiteria I'm not sure I understand the need for a package to expose its name. What do you mean by "conditionally accessing packages" ? Wouldn't users simply import the package and use it directly in their document ?

zral0kh commented

2026-03-12 23:07:54 +00:00

Hi, please take a look at this issue i would like to do: https://github.com/touying-typ/touying/issues/302

And a more general answer to why exposing names is useful:
It allows other packages to build on top of packages if they are imported / if the user wants to use them.

E,g, for touying this would allow us to use animated graphics without the user having to specify the bindings bc we can put them in the code. The user only needs to specify sth like reduce(MODULE), which based on the module would do different things. But to properly recognize the module we need the name.

Hi, please take a look at this issue i would like to do: https://github.com/touying-typ/touying/issues/302 And a more general answer to why exposing names is useful: It allows other packages to build on top of packages if they are imported / if the user wants to use them. E,g, for touying this would allow us to use animated graphics without the user having to specify the bindings bc we can put them in the code. The user only needs to specify sth like `reduce(MODULE)`, which based on the module would do different things. But to properly recognize the module we need the name.

HEL referenced a pull request that will close this issue

2026-06-30 16:34:20 +00:00

chore: expose package name #19

HEL closed this issue

2026-06-30 16:34:29 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: HEL/circuiteria#17