Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactored docs (markdown files) to be MDX v3 compatible #1406

Closed
wants to merge 2 commits into from

Conversation

DILPREET1910
Copy link

@DILPREET1910 DILPREET1910 commented Oct 28, 2024

Summary

Updated docs—markdown files to be MDX v3 compatible as required by docusaurus v3.5.2
Output of npx docusaurus-mdx-checker:
image

Next Steps

  • If these changes look good, I can proceed with bumping the Docusaurus version to 3.5.2.
  • Should i add MDX v3 compatibility check to the github CI/CD pipeline?

on track to fix: #1371

@DILPREET1910 DILPREET1910 requested a review from a team as a code owner October 28, 2024 17:28
Copy link

linux-foundation-easycla bot commented Oct 28, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

Copy link

netlify bot commented Oct 28, 2024

Deploy Preview for fdc3 ready!

Name Link
🔨 Latest commit e894b9d
🔍 Latest deploy log https://app.netlify.com/sites/fdc3/deploys/672b02314f623d0008add76e
😎 Deploy Preview https://deploy-preview-1406--fdc3.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -1,4 +1,4 @@
# <a href='http://fdc3.finos.org/toolbox/fdc3-explained'><img src='logo.png' alt='FDC3 Explained Logo'></a>
# <a href='http://fdc3.finos.org/toolbox/fdc3-explained'><img src='logo.png' alt='FDC3 Explained Logo'/></a>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doubling up on closing the tag

Suggested change
# <a href='http://fdc3.finos.org/toolbox/fdc3-explained'><img src='logo.png' alt='FDC3 Explained Logo'/></a>
# <a href='http://fdc3.finos.org/toolbox/fdc3-explained'><img src='logo.png' alt='FDC3 Explained Logo'/>

Copy link
Contributor

@kriswest kriswest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @DILPREET1910, many thanks for taking this on. We have another overlapping PR #1409 that also addresses #1371 which we may need to combine with this one - there are merits to both and corrections are needed in both. It might be worth comparing the two PRs, see:

In particular, take a look at the script that generates the /docs/context/ref* pages in the latest version, see:
https://github.com/DILPREET1910/FDC3/blob/7ff9414ba88af3f9811f4e4d85795f9cf8062290/website/schema2Markdown.js#L186

As that script is not updated, your corrections to the context ref page in the main/unreleased version will be lost on deploy.


## Type

`fdc3.action`

## Properties

<details>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A previous PR did not include generated code for this, not a change created in this PR and can be ignored.

@@ -17,7 +17,7 @@ In addition to handling requests to plot charts, a charting application may use

## Schema

<https://fdc3.finos.org/schemas/next/context/chart.schema.json> ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chart.schema.json))
[https://fdc3.finos.org/schemas/next/context/chart.schema.json](https://fdc3.finos.org/schemas/next/context/chart.schema.json) ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chart.schema.json))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes like this will be wiped out when these pages are regenerated by /website/schema2markdown.ts ... That script needs adjusting and using to make these changes

| `style` | string | No | one of: `'line'`, `'bar'`, `'stacked-bar'`, `'mountain'`, `'candle'`, `'pie'`, `'scatter'`, `'histogram'`, `'heatmap'`, `'custom'` |
| `otherConfig`* | object | No | `{ /* unstandardized additional config */}` |
| `otherConfig`* | object | No | `\{ /* unstandardized additional config */\}` |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because its not wrapped in a <pre> tag the escape on this line becomes visible in the output:
image

Probably best to add the <pre> tag

@@ -21,7 +21,7 @@ https://fdc3.finos.org/schemas/2.0/email.schema.json
| Property | Type | Required | Example Value |
|-------------------|---------------------------------------|----------|---------------------|
| `type` | string | Yes | `'fdc3.email'` |
| `recipients` | fdc3.contact or fdc3.contactList | Yes | { type: "fdc3.contact", name: "John Doe", id: { "email": "[email protected]"}} |
| `recipients` | fdc3.contact or fdc3.contactList | Yes | \{ type: "fdc3.contact", name: "John Doe", id: \{ "email": "[email protected]"\}\} |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wrap example in a <pre> tag


## Details

| Property | Type | Required | Example Value |
|-------------------|-------------------------------------------|----------|-------------------------|
| `type` | string | Yes | `'fdc3.message'` |
| `text` | map of string mime-type to string content | No | { text/plain: 'Hello' } |
| `text` | map of string mime-type to string content | No | \{ text/plain: 'Hello' \} |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should probably be wrapped in a pre tag

sivaprasadanakarla added a commit to sivaprasadanakarla/FDC3 that referenced this pull request Nov 6, 2024
@DILPREET1910
Copy link
Author

Thanks for the review @kriswest.
I noticed that @sivaprasadanakarla has created a new PR #1418 that includes the recommended changes. More than happy to help with further adjustments, reviews and testing on that PR.

Closing this PR in favor of #1418

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade FDC3 website to docusaurus >=3.5.2
2 participants