Get current URL in custom component

Each of my blog posts contains the markdown…

See a typo? You can fix it by editing [this file](https://github.com/bender2k14/tyson-williams-blog/blob/master/src/markdown/2020-07-15_naming_is_impossibly_hard.md) and then sending me a [pull request](https://github.com/bender2k14/tyson-williams-blog/compare).

…except that 2020-07-15_naming_is_impossibly_hard is unique to each post.

I want to create a custom component to automate this work, but I don’t know where to get that string. Here is what I have tried.

Input:

return <ul>
         <li>document.location.href is {document.location.href}</li>
         <li>document.location.pathname is {document.location.pathname}</li>
         <li>window.location.href is {window.location.href}</li>
         <li>window.location.pathname is {window.location.pathname}</li>
         <li>document.URL is {document.URL}</li>
         <li>document.baseURI is {document.baseURI}</li>
      </ul>

Output:

- document.location.href is about:blank
- document.location.pathname is blank
- window.location.href is about:blank
- window.location.pathname is blank
- document.URL is about:blank
- document.baseURI is about:blank

Am I doing this wrong or is CODEDOC not setting those values (or both!)?

[loreanvictor]

Actually, on article cards, the information is not necessarily available. Imagine you have two articles referencing each other using Article cards, both either being built for the first time or their hero image / title / etc changing in the current build. Trying to resolve this information on the server side would only be possible by a deferred two-pass rendering which is too much added complexity for minor performance gain.

[TysonMN]

I am still only holding back to come across a use-case that would need the performance, to ensure that we add a method of providing global config to components in a manner suitable for actual use-cases.

Waiting for more use cases is a very good idea. This might be another use case.

I noticed that all the five article cards on my home page take a bit of time to fetch their data on the client. The URL in each article card is to another page in the same site…built by CODEDOC “at the same time” as the current page. In theory, this information is available on the server.

Maybe the article card could be optimized with behavior that depends on the provided URL. If the URL is to another page in the same site built by CODEDOC “at the same time”, then all the desired information is collected on the server. Otherwise, the URL is to a page on a different site, and the desired information is obtained on the client using the current behavior of the article card.