Skip to content

Documentation and language server file generation #245

Open
2 of 3 issues completed
Listed in
Open
2 of 3 issues completed
Parent:#150
Listed in
@makspll

Description

@makspll

Given we have function and type metadata available via traits and the various registries, we should generate a lanugage agnostic "binding" content format, which can then be transpilled to things like:

  • Documentation
  • Language server definition files

Tasks:

Sub-issues

Sub-issues

2 of 3 Issues completed

Activity

added this to the 2025 Goals milestone on Feb 1, 2025
makspll

makspll commented on Feb 1, 2025

@makspll
OwnerAuthor

The format should support:

  • fields
  • functions
  • types

Each type should be expressed together with stable type ID's, the "wrapper" types like Val Ref and Mut, names for fields and function arguments should be forwarded, and generic documentation strings too.

The types should also export as much information from the type registry as necessary

moved this from Planned to In progress in BMS Roadmapon Mar 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    In progress

    Development

    No branches or pull requests

      Participants

      @makspll

      Issue actions

        Documentation and language server file generation · Issue #245 · makspll/bevy_mod_scripting