dart_nvim_api 0.2.1
dart_nvim_api: ^0.2.1 copied to clipboard
A Neovim API for Dart allowing for communication between a Neovim instance and a Dart program. Can be used for creating Neovim plugins, Neovim frontend GUIs, etc.
0.1.0 #
- Initial version
0.1.1 #
- Make function names for the
Buffer,Tabpage, andWindowclasses camelcase. - Fix an issue where API functions which were supposed to return
a
Buffer,Tabpage, orWindowwould returnnullinstead.
0.1.2 #
- Additions
attachUifunction in theNeovimclass for attaching an external UI to Neovim.- Travis.
- Documentation for
Neovimclass (not finished yet, mainly waiting on neovim/neovim#1139 and a subsequent PR adding a way to get the documentation on each API function from Neovim). - Classes for each type of
ui_eventfrom Neovim. exampledirectory with a short example (shown in README).
- Changes
- Moved
Neovimclass fromlib/dart_nvim_api.darttolib/src/neovim.dartto be more consistent with idiomatic Dart library structure. - Updated README to show latest library version from pub.flutter-io.cn
- Moved
0.1.3 #
- Added
Session.fromCurrentStdinStdout()function and an optional flag (communicateWithParentProcess) to theNeovimclass (see docs for more info).
0.1.4 #
- Fixed an issue where functions which returned
Lists (e.g.Buffer().getLineswould throw an error sayingtype 'List<dynamic>' is not a subtype of type 'List<String>' in type castor similar.
0.2.0 #
Neovimclass has been renamed toNvim- Neovim instance is spawned via
await Nvim.spawn() - Now a Neovim instance that communicates to Neovim via current stdin/stdout is gotten with
await Nvim.child() - Buffer/Window/Tabpage APIs are within the Nvim API, so
await nvim.bufGetName(buf)is used instead ofawait buf.getName(), and likewise for the window and tabpage APIs. - More/better tests
- Various internal changes
0.2.1 #
- Errors from Neovim when calling API functions are now forwarded to the caller via exceptions.