Flower pot fixes #2731
No reviewers
Labels
No Label
#P1 CRITICAL
#P2: HIGH
#P3: elevated
#P4 priority: medium
#P6: low
#Review
annoying
API
bug
code quality
combat
commands
compatibility
configurability
contribution inside
controls
core feature
creative mode
delayed for engine release
documentation
duplicate
enhancement
environment
feature request
gameplay
graphics
ground content conflict
GUI/HUD
help wanted
incomplete feature
invalid / won't fix
items
looking for contributor
mapgen
meta
mineclone2+
Minecraft >= 1.13
Minecraft >= 1.17
missing feature
mobile
mobs
mod support
model needed
multiplayer
Needs adoption
needs discussion
needs engine change
needs more information
needs research
nodes
non-mob entities
performance
player
possible close
redstone
release notes
schematics
Skyblock
sounds
Testing / Retest
tools
translation
unconfirmed
mcl5
mcla
Media missing
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: VoxeLibre/VoxeLibre#2731
Loading…
Reference in New Issue
No description provided.
Delete Branch "flowerpot-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
minetest.features.use_texture_alpha_string_modes
What format are the type annotations?
https://github.com/sumneko/lua-language-server
Using the folowing headers:
https://github.com/AFCMS/minetest_vscode_lua
Even if you don't use a compatible editor, it gives an easy comprension of function params.
So what if the next person adds their own format to make it compatible with their editor?
I'm generally not a fan of this stuff tbh. and tend to remove it when I work on something. I just do not see the big benefit and it does have some cost (particularly everyone in the future has to deal with it in some way) our files are already so full of often quite useless comments.
I mean it's fine if you do it for stuff you're working on i guess (if it stays at just the 1 line per function) but please don't expect anyone else to accomodate your IDE.
There are practically no competitors.
EmmyLua/derivated (which I use and which have a decent editor support) and LuaDoc, which have no editor support and allow much less complex types
It support VSCode, NeoVIM, command line, etc
7e861585e5
to5719637ee7
Well there is one "competitor" that seems to be used A LOT: not doing any of this ^^
I mean idk what an ide even makes of this – ultimately the question is does it save you more time than it costs to add and maintain this stuff?
I would say in my humble programming experience this stuff has cost me a lot more time than it ever saved.
The thing about these "helpful" features like e.g. autocompletion is that you forget things - and quickly - and then when you least expect it you're stranded with nano and a slow internet connection so you cant even quickly look something up which you would have memorized if it hadn't been for your super IDE ^^
looks way nicer now
try to make the reformatting stuff separate commits next time though. That makes it a lot easier for people in the future to understand changes that were made.
I personally use it a lot, and it REALLY helps me.
With a super simple header like what I added to mcl_title, it is much less error prone.
But with a real API header file with documentation and classes it gets really really helpful:
Once you learned the basic way these anotations works, you spend very little time adding basic one like I did in mcl_title (it takes me no more than 30s/function for these ones, and often much less)
I simply not develop without good tools. The worst editor I used for minetest development was Notepad++ on windows, but it still had a way to add functions to autocomplete (was just string completion, but at least help you not using undefined functions).