Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFS Gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
firmware
FFS Gluon
Commits
2541d0a0
Commit
2541d0a0
authored
5 years ago
by
rubo77
Committed by
Martin Weinelt
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
docs: Add information how to automatically check your code with luacheck
parent
a8e5a822
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/dev/basics.rst
+6
-4
6 additions, 4 deletions
docs/dev/basics.rst
with
6 additions
and
4 deletions
docs/dev/basics.rst
+
6
−
4
View file @
2541d0a0
...
...
@@ -54,16 +54,18 @@ commits, making `git reflog` the only way to recover them!
Development Guidelines
----------------------
l
ua should be used instead of sh whenever sensible. The following criteria
L
ua should be used instead of sh whenever sensible. The following criteria
should be considered:
- Is the script doing more than just executing external commands? if so, use
l
ua
- Is the script parsing/editing json-data? If so, use
l
ua for speed
- Is the script doing more than just executing external commands? if so, use
L
ua
- Is the script parsing/editing json-data? If so, use
L
ua for speed
- When using sh, use jsonfilter instead of json_* functions for speed
Code formatting may sound like a topic for the pedantic, however it helps if
the code in the project is formatted in the same way. The following rules
the code in the project is formatted in the same way. The following
basic
rules
apply:
- use tabs instead of spaces
- trailing whitespaces must be eliminated
If you add Lua scripts to gluon, check formatting with ``luacheck``.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment