v2.1.0

What's Changed

• Service mutual dependencies by @NobleDraconian in #75

Full Changelog: v2.0.0...v2.1.0

v2.0.0

• The framework's structure has been changed to be compatible with wally, a package manager for Roblox. This means that the framework is now a wally package! The package can be viewed here.
• The Enum APIs have been deprecated and should not be used.
• The framework's execution model has been changed slightly. In order to run the framework, explicit execution is now required via the DragonEngine:Run() API.
• The framework now has a documentation site! It can be viewed here.

v0.1.0-rc.7

What's Changed

• Add expanded logging APIs by @NobleDraconian in #70

Full Changelog: v0.1.0-rc.6...v0.1.0-rc.7

v0.1.0-rc.6

This release features a small patch for a problem that was missed in the v0.1.0-rc.5 release (#68).

v0.1.0-rc.5

This release changes how the framework loads its own resources internally (#65), and also removes some unnecessary services & controllers (#67).

v0.1.0-rc.4

This release adds support for loading modules that are inside nested folders (#54), and fixes a bug (#55) regarding module lazy-loading.

v0.1.0-rc.3

This release adds missing client functionality, namely the GetService() method.

v0.1.0-rc.2

This release contains a hot-fix regarding settings loading (#52). Developer-specified settings should now load properly when the framework runs.

v0.1.0-rc.1

This pre-release includes a lot of changes to the framework as a whole.
Changes include:

• Module APIs have been rewritten, and modules are now lazy-loaded (#50).
• APIs like GetService(), GetController() and GetModule() are now the conventional method of accessing framework resources. Directly referencing internal tables such as DragonEngine.Modules is not safe as the internal table structure may change in the future. The APIs ensure a safe way to access these resources.
• The framework is now broken down into 3 packages via rojo project files : the server, the client, and the core/shared part.
• A bug regarding when the framework exposes itself to the global environment has been fixed. The framework will not expose itself to shared until it is finished loading.