# 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:** 6
**Page:** 1
### Author:  [@scheinerman](https://discourse.julialang.org/u/scheinerman)
#### Post date: [October 21, 2024, 1:50pm UTC](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531/1 "2024-10-21T13:50:37Z")
I have found that tagging some of my functions as `public` causes two problems. First, JuliaFormatter fails. Second, the documentation I built with Documenter doesn’t migrate to [docs.juliahub.com](http://docs.juliahub.com).
---
### Author:  [@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")
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.
---
### Author:  [@Eben60](https://discourse.julialang.org/u/Eben60)
#### Post date: [October 21, 2024, 9:43pm UTC](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531/3 "2024-10-21T21:43:26Z")
> [@mbauman](#):
>
> should set Julia’s compat to “1.11” in your project
As an additional information: I’ve set the Julia’s compat to “1.10” for the package itself (ShareAdd.jl), and “1.11” for the `Project.toml` in the `docs` subfolder. Unfortunately, Documenter-built documentation does not appear on the `juliahub.com`
---
### Author:  [@mbauman](https://discourse.julialang.org/u/mbauman)
#### Post date: [October 21, 2024, 9:52pm UTC](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531/4 "2024-10-21T21:52:28Z")
Yeah, sorry, I should’ve been clearer — my second sentence doesn’t (yet!) affect JuliaHub’s behavior here. You can see the build logs by clicking the little \enclose{circle}{\text{i}} button:
You’ll see that there’s a message in there warning that `julia version requirement for project not satisfied`.
---
### Author:  [@j-fu](https://discourse.julialang.org/u/j-fu)
#### Post date: [October 21, 2024, 10:36pm UTC](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531/5 "2024-10-21T22:36:43Z")
You can reroute Juliahub’s documentation link, see
> **[GitHub - JuliaDocs/DocumentationGeneratorRegistry](https://github.com/JuliaDocs/DocumentationGeneratorRegistry)**
>
> Contribute to JuliaDocs/DocumentationGeneratorRegistry development by creating an account on GitHub.
---
### Author:  [@Eben60](https://discourse.julialang.org/u/Eben60)
#### Post date: [October 22, 2024, 3:09pm UTC](https://discourse.julialang.org/t/juliaformatter-juliahub-docs-and-the-public-keyword/121531/6 "2024-10-22T15:09:24Z")
> [@mbauman](#):
>
> (_yet_!)
any estimation of the timeframe?