You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this definition is then interpreted by a LuaHTMLFrontend
Knowing how wrappers and primitives are handled in the Lua case, the generator produces html docs including a page for the world item
If the provider cannot express a certain type, it can fall back on some sort of plain default description (but this shouldn't happen, for compatibile backends and frontends)
This can be done at compile time thanks to bevy_api_gen, we can search the codebase for either custom attributes to generate the doc definitions, and they can also be produced manually for hand-written types
The text was updated successfully, but these errors were encountered:
Ideally we could have a unified documentation data definition language, which would describe the provided API for a provider.
We could then have different frontends which interpret that data for a target language.
As an example:
String
argumentLuaHTMLFrontend
world
itemThe text was updated successfully, but these errors were encountered: