Andreas/evennia
1
0
Fork 0
mirror of https://github.com/evennia/evennia.git synced 2026-03-17 05:16:31 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Doc refactor/renaming

Browse source
This commit is contained in:
Griatch 2020-07-11 10:41:33 +02:00
parent 9d8e8d7693
commit b5b265ec3b
115 changed files with 518 additions and 434 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/source/Coding/Coding-Introduction.md
View file

@ -39,7 +39,7 @@ available at the top level of Evennia's "flat API". See the [flat API](../Evenn
info on how to explore it efficiently.
You can complement your exploration by peeking at the sections of the much more detailed
[Evennia Component overview](../Component/Component-Overview). The [Tutorials](../Howto/Howto-Overview) section also contains a growing collection
[Evennia Component overview](../Components/Components-Overview). The [Tutorials](../Howto/Howto-Overview) section also contains a growing collection
of system- or implementation-specific help.
### Use a python syntax checker

2
docs/source/Coding/Quirks.md
View file

@ -64,7 +64,7 @@ update the database you'd need to explicitly re-assign the updated data to the `
### Commands are matched by name *or* alias
When merging [command sets](../Component/Commands) it's important to remember that command objects are identified
When merging [command sets](../Components/Commands) it's important to remember that command objects are identified
*both* by key *or* alias. So if you have a command with a key `look` and an alias `ls`, introducing
another command with a key `ls` will be assumed by the system to be *identical* to the first one.
This usually means merging cmdsets will overload one of them depending on priority. Whereas this is

2
docs/source/Coding/Unit-Testing.md
View file

@ -153,7 +153,7 @@ class in the same module to get access to the command-specific utilities mention
### Unit testing contribs with custom models
A special case is if you were to create a contribution to go to the `evennia/contrib` folder that
uses its [own database models](../Concept/New-Models). The problem with this is that Evennia (and Django) will
uses its [own database models](../Concepts/New-Models). The problem with this is that Evennia (and Django) will
only recognize models in `settings.INSTALLED_APPS`. If a user wants to use your contrib, they will
be required to add your models to their settings file. But since contribs are optional you cannot
add the model to Evennia's central `settings_default.py` file - this would always create your