Hyperswitch github3/17/2023 If a plugin reloads, it's called again and the menu is refreshed.Īllows you to decorate Electron's BrowserWindow options when a new window is created. Invoked with the Electron's Menu template. Allows you to decorate the user's environment by returning a modified environment object. Useful for themeing or custom parameters for your plugin. Allows you to decorate the user's configuration. Invoked when a plugin is removed by the user. If a plugin reloads, it's invoked again with the existing windows. If a plugin reloads, it's invoked again with the existing app. Your module has to expose at least one of these methods: You can find additional details about plugin development in the Hyper repository. The only knowledge that is therefore required to successfully extend Hyper is that of its underlying open source libraries. Instead of exposing a custom API method or parameter for every possible customization point, we allow you to intercept and compose every bit of functionality! The extension system is designed around composition of the APIs we use to build the terminal: React components and Redux actions. Available options are: true, false, "left"Įxtensions are universal Node.js modules loaded by both Electron and the renderer process. Available options are: true, falseĬhange the position/visibility of the window controls. If true, Hyper will be set as the default protocol client for SSHĬhange the behaviour of modifier keys to act as meta keyĬhange the visibility of the hamburger menu. If true, on right click selected text will be copied or pasted if no selection is present (true by default on Windows) If true, selected text will automatically be copied to the clipboard The number of rows to be persisted in terminal buffer for scrolling The default width/height in pixels of a new window The names of the keys represent the "ANSI 16", which can all be seen in the default config.Ī path to a custom shell to run when Hyper starts a new sessionĪn object of environment variables to set before launching shell hyper.js and add it to plugins module.exports = Ī list of overrides for the color palette. We encourage everyone to include hyper in the keywordsfield in package.json. ExtensionsĮxtensions are available on npm. In the future, we anticipate the community will come up with innovative additions to enhance what could be the simplest, most powerful and well-tested interface for productivity. In the beginning, our focus will be primarily around speed, stability and the development of the correct API for extension authors. The JSON spec should also be statically exposed, and the swagger-ui lib should be configured to request the JSON spec.The goal of the project is to create a beautiful and extensible experience for command-line interface users, built on open web standards. A route needs to be defined that would statically serve the dist content of the swagger-ui lib, possibly making some amendments on it, just like we do for RESTBase, and example could be found in. The implementation should be pretty straightforward. We need to integrate it in the service template. That can be accomplished with the SwaggerUI package to obtain a result similar to Wikipedia's REST API documentation. The service template makes use of Swagger specifications in order to automatically test the service during the test phase as well as ensure that the service checker script we have in production can be used to monitor it regularly.Įven though we use Swagger, the service template itself does not automatically expose the information contained in the specification in a nice self-documented way via swagger-ui library.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |