fix doctype #1300
fix doctype #1300
Conversation
|
@chillenberger I see your PR around this too, thought it'd be able to fix than report the missing |
|
I was thinking about just using the tools from Pathbuf to determine if it is doc, blog, or careers. |
|
Could also pass in the collection to avoid having to parse at all. Or make
this a collection method.
…On Tue, Jan 23, 2024 at 12:09 PM Dan ***@***.***> wrote:
I was thinking about just using the tools from Pathbuf to determine if it
is doc, blog, or careers.
let doc_type = match path.strip_prefix(config::cms_dir()) { Ok(path) => {
match path.into_iter().next() { Some(dir) => { match
&PathBuf::from(dir).display().to_string()[..] { "blog" =>
Some(DocType::Blog), "docs" => Some(DocType::Docs), "careers" =>
Some(DocType::Careers), _ => None } }, _ => None } }, _ => None, };
—
Reply to this email directly, view it on GitHub
<#1300 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACDNHJ7OKIER2Z3XU7HHITYQAKIBAVCNFSM6AAAAABCHS6X2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWHA2DCNBUGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
It felt too specific to the doc to put in collection and I wanted to minimize the amount of info the caller needed since I wasn't sure what Silas would have access too. Here is what I am thinking #1301 |
No description provided.