-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add "wireframe" for generated event docs #454
Conversation
docs/api/thermostats/README.md
Outdated
Key of the [climate preset](../../capability-guides/thermostats/creating-and-managing-climate-presets) that was activated. | ||
</details> | ||
<details> | ||
<summary>is_fallback_climate_preset <code>boolean</code></summary> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other things are not being rendered inside these expand/collapse blocks either. See https://docs.seam.co/latest/api/acs/systems#location for an example of "`" not rendering as code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The details block is HTML, right? If so, do we need to use HTML tags inside to get it to render?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other things are not being rendered inside these expand/collapse blocks either. See docs.seam.co/latest/api/acs/systems#location for an example of "`" not rendering as code.
Sounds like a GitBook issue and we will need to add a markdown render step for content that is inside html tags.
Overall looks good!
|
Yay!
Was wondering the same thing. Can we try HTML instead of MD inside these blocks?
I vote for repeating them for completeness if it's something that can be done programmatically/automatically. |
|
||
<details> | ||
<summary>method <code>enum</code></summary> | ||
Method used to adjust the thermostat manually. `seam` indicates that the Seam API, Seam CLI, or Seam Console was used to adjust the thermostat. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@razor-x OK, this seems inconsistent with the other page that has expand/collapse blocks, but using "``" or "" works here to format text as code.
docs/api/thermostats/README.md
Outdated
</details> | ||
<details> | ||
<summary>upper_limit_celsius <code>number</code></summary> | ||
Upper temperature limit, in °C, defined by the set <a href="https://docs.seam.co/latest/capability-guides/thermostats/setting-and-monitoring-temperature-thresholds">threshold</a>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@razor-x As you saw, the relative URL does not work. Using the full/absolute URL here does not work either. What should we do?
@razor-x Given the GitBook limitations that we've found, what's the next step for this PR? |
If links are unable to render inside the expandable section, we only have two choices (unless we contact GitBook support and they make it work)
|
@razor-x Of these choices, I vote for 2. If also like to see what happens if I add an expand/collapse with a link through the GitBook UI. I wonder if it works there. |
@razor-x Of course, it works when added through the GitBook GUI... and it looks identical to what we added through GitHub (that did not work). Working: https://docs.seam.co/latest/api/noise_sensors#events |
Conclusions:
|
@razor-x What's the next step for this PR? Should we merge it, or should the generation template additions go in this PR too? |
We can't merge this one because it has to be owned by the generation. But this PR will be used as a reference to update the template to match this format. |
@razor-x Should we close this PR now? |
No description provided.