re-export syntax #443
amitu
started this conversation in
Ideas & RFCs
Replies: 1 comment
-
This will remain in effect even after https://github.com/orgs/fastn-stack/discussions/1816. The module in which something is documented is where it will be visible. Eg foo.ftd's foo-component is re-exported in index.ftd, it is technically accessible from both both index.ftd and foo.ftd, so the docs folder will decide if it is meant to be public in index.ftd or foo.ftd. If we are using inline documentation, where ever the inline documentation is found that will be its public location. This means we can define foo-component in foo.ftd and forward declare with docs in index.ftd, if we want world to see foo-component in index.ftd. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When importing other modules, a module can re-export things from that module:
In this case, say this was
bar.ftd
,bar.hello
andbar.world
now point tofoo.hello
andfoo.world
.We can also re-export everything using
*
:Beta Was this translation helpful? Give feedback.
All reactions