self documenting components, types and variables #466
amitu
started this conversation in
Ideas & RFCs
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We need documentation support in ftd. We do not believe in putting documenting along with code, as that makes translation difficult. So documentation has to live in another file,
foo.ftdoc
for everyfoo.ftd
. How wouldfoo.ftdoc
would look like?We would definitely want to include samples, especially for components, so one can auto generate component browser etc, and have previews.
We can put all the
.ftdoc
files in another fpm package, so one can translate the documentation package as well using upcoming fpm translation support.About
ftdoc
fileEach module will have a corresponding documentation file. For
mod.ftd
we will havemod.ftdoc
.A
mod.ftdoc
file can refer to individual files for each symbol also,[email protected]
, in case the module is too big.View Component Source
Source feature
View Children Source
If external children has been passed to some component, we want to see the source code for them.
Beta Was this translation helpful? Give feedback.
All reactions