I love the way the openapi.yaml renderer works. Is there a way to somehow hook in a user-created file renderer like that?
Thanks
Georg
I love the way the openapi.yaml renderer works. Is there a way to somehow hook in a user-created file renderer like that?
Thanks
Georg
I would also like this. The combination of custom renderers and custom merge or diff tools would allow to handle other than text-formatted documents.
This probably should be combined with a way to specify the MIME type of documents in you repository that is understood by GitLab. For instance, Gitlab already uses the .gitattributes file. Why not define MIME-types in that file, and link MIME-types (inferred or from that file) to renderers, mergers, and differs?
Even without renderers, better MIME-type support would make it easier to work with GitLab hosted files, e.g. by offering the correct MIME-type to the browser and let the browser decide what tool to use to open the file.
This would much improve the usability of GitLab in other contexts, including those in which for instance file formats are enforced for compliance reasons, and make it more useable for less code-oriented people (such as from QM departments).