# DocC and extensions?

**URL:** <https://forums.swift.org/t/docc-and-extensions/53132>\
**Category:** Using Swift\
**Tags:** documentation\
**Created:** [October 28, 2021, 1:59pm UTC](https://forums.swift.org/t/docc-and-extensions/53132 "2021-10-28T13:59:58Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ethankusters](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ethankusters/32/19078_2.png) [@ethankusters](https://forums.swift.org/u/ethankusters)\
**Post date:** [October 29, 2021, 3:52pm UTC](https://forums.swift.org/t/docc-and-extensions/53132/3 "2021-10-29T15:52:19Z")

</div>

> DocC currently does not support references to symbols/types defined in other modules, including symbols defined as extensions in the current module.

@Mordil is correct here. Although, I would separate those as two separate issues. Linking to symbols defined in other modules is a new feature we would would definitely like to support in Swift-DocC (@Mordil a feature request on [bugs.swift.org](http://bugs.swift.org/) would be great!), while I would view the behavior @robnik described as a bug. Those symbols are defined in your current module, so DocC should support them even without the cross-module linking feature.

@robnik if you could file a bug on [bugs.swift.org](http://bugs.swift.org/) with the behavior you’re seeing as well as your proposed solution for link syntax that would be really appreciated! One of things we need to work through here is the UX of how extension symbols would be rendered and linked to.

---

_[View the full topic](https://forums.swift.org/t/docc-and-extensions/53132)._