33Contributions are welcome! To keep everything clean and tidy, please follow the
44guidelines below.
55
6+ # Development setup
7+
8+ View [ mise.toml] ( ./mise.toml ) for tasks and their implementation.
9+ ``` bash
10+
11+
12+ ```
13+
614## Code Style
715
816This is open for debate, but here is the current style choices being observed:
@@ -12,9 +20,6 @@ This is open for debate, but here is the current style choices being observed:
1220- other OOP things, like method names should use camelCase
1321- BUT we don't currently have any OOP parts and I don't think we want any
1422
15- I prefer ` local name = function() ` over ` local function name() ` , just to be
16- consistent with the ` M.name = function() ` exports.
17-
1823### StyLua
1924
2025We use (StyLua)[ https://github.com/JohnnyMorganz/StyLua ] to enforce consistency
@@ -50,10 +55,10 @@ current strategy is to maintain:
5055 in comments. This is the bare minimum documentation for an option.
5156- The README contains "back of the box" high level overview of features. It is
5257 meant for people trying to decide if they want to install this plugin or not.
53- It should include references to the help file for more information:
58+ It should include references to the help file for more information:
5459 ` :h neo-tree-setup `
5560- Whether something should be mentioned in the README or just in the help file
56- is a completely subjective judement call that is made on a case by case basis
61+ is a completely subjective judgement call that is made on a case by case basis
5762 based on how many people are likely to be interested in that information.
5863- The vim help file [ doc/neo-tree.txt] ( doc/neo-tree.txt ) is the definitive
5964 reference and should contain all information needed to configure and use the
0 commit comments