Chris Duncan (Oct 10 2022 at 22:31): Chris Duncan (Oct 10 2022 at 22:31):Currently, Roc has a limited set of metadata it can express. In the platform's main.roc file, you can describe the platform's name, the modules it depends on, and the main function. For an application, you can also describe the platform it depends on.
How will the user express other metadata they care about? For example: versioning, dependencies the main file doesn't use, authors, contributors, links (homepage, repository, bugs, donations, etc), license, description, etc.
Richard Feldman (Oct 10 2022 at 22:36):the same way the other things in the header are today (e.g. imports)
Chris Duncan (Oct 10 2022 at 22:41):Is there a document describing the possibilities. For example, experimenting today I discovered that I can have an interface file with an empty array of exposes and imports to test functions based solely on Roc's Standard Library, yet I can't have a file that omits them. It would be great to consult a document that explains what currently can and cannot be done.
Richard Feldman (Oct 10 2022 at 23:16):makes sense - I'll add that to the list of things to document! :+1:
Last updated: Jun 16 2026 at 16:19 UTC