The Philosophy Goal Implementation links all point to One-to-One

[louy2]

Issue Description

What was unclear/insufficient/not covered in the documentation

The Philosophy, Goal, Implementation links under One-to-Many and Many-to-Many all point to the headings with the same names under One-to-One.

If possible: Provide some suggestion on how we can enhance the docs

Fix the links to point to their corresponding headings.

Additional context

Issue Template Checklist

Is this issue dialect-specific?

• No. This issue is relevant to Sequelize as a whole.
• Yes. This issue only applies to the following dialect(s): XXX, YYY, ZZZ
• I don't know.

Would you be willing to resolve this issue by submitting a Pull Request?

• Yes, I have the time and I know how to start.
• Yes, I have the time but I don't know how to start, I would need guidance.
• No, I don't have the time, although I believe I could do it if I had the time...
• No, I don't have the time and I wouldn't even know how to start.

[papb]

Hello! Thanks for reporting this. This seems a nontrivial bug from esdoc since it generates the heading 'names' simply from their own text, and since the texts are identical, this ends up happening.

Maybe we can perform a manual fix...

[papb]

Yes, I have the time but I don't know how to start, I would need guidance.

Awesome. I suggest you see how I've done some documentation transforms and write your own transform to update the duplicate heading links to something else (perhaps adding suffixes such as -2, -3 to the ones that aren't the first)

[louy2]

Found the offending code in the publish html plugin, but not sure how much work it is to swap it out.

https://github.com/esdoc/esdoc-plugins/blob/master/esdoc-publish-html-plugin/src/Builder/util.js#L65

  const renderer = new marked.Renderer();
  renderer.heading = function (text, level) {
    const id = escapeURLHash(text);
    return `<h${level} id=${id}>${text}</h${level}>`;
  };

[louy2]

Oh, you forgot to specify cheerio in the dev dependencies. Interesting how you could use it from transitive dependency position. I'm using pnpm which doesn't allow that.