speced / speced/respec

latestVersion set to null does not remove "Latest published version" ?

Open
#5,332 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
806
Forks
434
Avg merge
1d 21h
Merged PRs (30d)
32

Description

Description of problem

Documentation says that setting latestVersion to null should remove the "Latest published version" completely. But it seems not.

URL to affected spec or repo:

Example page at https://shapes.performing-arts.ch/authorities/

What happened (e.g., it crashed)?:

ReSpec config:

<script id="initialUserConfig" type="application/json">{
  "preProcess": [
    null,
    null
  ],
  "specStatus": "base",
  "latestVersion": null,
  "maxTocLevel": 2,
  "license": "w3c-software-doc",
  "editors": [
    {
      "name": " "
    }
  ],
  "otherLinks": [
    {
      "key": "Version: ",
      "data": [
        {
          "value": "1.1.0",
          "href": ""
        }
      ]
    }
  ],
  "url": "https://xls2rdf.sparna.fr/rest/convert?url=https://docs.google.com/spreadsheets/d/1OBpZgVwO_0hLNbX0bXVFCetQBQjPeNFR/export?format=xlsx&noPostProcessings=true",
  "includeDiagram": true,
  "language": "en",
  "publishISODate": "2026-06-08T00:00:00.000Z",
  "generatedSubtitle": "08 June 2026"
}</script>

Displayed:

Image

Expected behavior (e.g., it shouldn't crash):

I would have expected the "Latest published version" line to be removed completely instead of showing "none"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue using the example page at https://shapes.performing-arts.ch/authorities/ and its ReSpec configuration, focusing on the latestVersion: null setting. Trace where the “Latest published version” line is rendered and verify that the completed behavior omits the line rather than displaying “none”.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.