This repository was archived by the owner on Dec 12, 2024. It is now read-only.
feat: examples of all send modes #284
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Any progress here? |
2 similar comments
|
Any progress here? |
|
Any progress here? |
|
This PR is being deprecated due to the upcoming transition to the Starlight documentation framework. Once we get the new framework, the approach to resolving this issue will likely change, so this PR is obsolete and must be re-made. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP: Working out potential structure. Thing is, there are 2^4 combinations for so-called optional flags and 3 base modes (including none), which makes the whole page a bit unwieldy (48 examples of
send()).I'll figure out something, there was a way to make a dynamic code block via Nextra (the doc theme we're using) even in SSG mode.
Closes tact-lang/tact#1073