# JuliaFormatter, JuliaHub docs, and the public keyword

**URL:** <https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531>\
**Category:** General Usage\
**Tags:** documenter, juliaformatter\
**Created:** [October 21, 2024, 1:50pm UTC](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531 "2024-10-21T13:50:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [October 21, 2024, 3:13pm UTC](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531/2 "2024-10-21T15:13:08Z")

</div>

Ah, yes, I think JuliaHub is currently building all its docs using v1.10. If you want to use `public`, you should set Julia’s compat to “1.11” in your project or use one of the compat-ified equivalents:

> [@Is Compat.jl worth it for the \`public\` keyword?](https://discourse.julialang.org/t/is-compat-jl-worth-it-for-the-public-keyword/119041):
>
> With the introduction of public by @Lilith, many packages will want to mark their unexported public symbols that way. Since public is only available in Julia 1.11, the current recommended way to do this in 1.10 is with the Compat.jl package. Before we add it everywhere, I’m wondering if there are any negative side effects to it? @stevengj seems to think it’s fine but I’d love to get other opinions. In particular, it depends on 4 stdlibs: Dates, LinearAlgebra, TOML and UUIDs.

---

_[View the full topic](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531)._