godot-fmod - Godot with FMOD integration

Age	Commit message (Collapse)	Author
2021-10-14	Implement toast notifications in the editor	Gilles Roudière

2021-10-06	GDScript: Make all warnings enabled in test generation	George Marques
	The test generation doesn't initialize the language (since it's already initialized in main), but it still needs the warning enabled so it matches the actual tests.
2021-09-13	Fix an undefined behaviour	ThreeRhinosInAnElephantCostume

2021-09-13	Merge pull request #52068 from ThreeRhinosInAnElephantCostume/fixgdscript	Rémi Verschelde
	Fix parse error on statement-less files with only newlines, add a warning for empty files.
2021-09-11	Fix error on parsing statement-less GDScript files,	ThreeRhinosInAnElephantCostume
	add an empty file warning, add relevant tests.
2021-08-26	Use OrderedHashMap for autoloads to preserve order	Lyuma

2021-07-23	Use C++ iterators for Lists in many situations	Aaron Franke

2021-06-19	Rename `instance()`->`instantiate()` when it's a verb	Lightning_A

2021-06-11	Rename Reference to RefCounted	Pedro J. Estébanez

2021-06-11	Core: Move DirAccess and FileAccess to `core/io`	Rémi Verschelde
	File handling APIs are typically considered part of I/O, and we did have most `FileAccess` implementations in `core/io` already.
2021-05-24	GDScript: Fix error handler for tests	George Marques
	This changes the error message to be more clear on the output files and also fixes an issue with the relative path of the offending file that was not trimmed correctly.
2021-04-26	Remove uses of `auto` for better readability and online code reviews	Hugo Locurcio
	The current code style guidelines forbid the use of `auto`. Some uses of `auto` are still present, such as in UWP code (which can't be currently tested) and macros (where removing `auto` isn't easy).
2021-04-08	Add runner for GDScript testing	George Marques
	This is meant for testing the GDScript implementation, not for testing user scripts nor testing the engine using scripts. Tests consists in a GDScript file and a .out file with the expected output. The .out file format is: expected status (based on the enum GDScriptTest::TestStatus) on the first line, followed by either an error message or the resulting output. Warnings are added after the first line, before the output (or compiler errors) if the parser pass without any error. The test script must have a function called `test()` which takes no argument. Such function will be called by the test runner. The test should not have any dependency unless it's part of the test too. Global classes (using `class_name`) are registered before the runner starts, so those should work if needed. Use the command `godot --gdscript-generate-tests godot-source/modules/gdscript/tests/scripts` to update the .out files with the current output (make sure the output are the expected values before committing). The tests themselves are part of the doctest suite so those can be executed with `godot --test`. Co-authored-by: Andrii Doroshenko (Xrayez) <xrayez@gmail.com>