DOC Document creating fixtures in custom DB tables #484
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GuySartorelli
commented
Mar 20, 2024
Comment on lines
-196
to
+199
| ## Fixtures for namespaced classes | ||
|
|
||
| You will need to use fully qualified class names in your YAML fixture files. In the above examples, they belong to the global namespace so there is nothing requires, but if you have a deeper DataObject, or it has a relationship to models that are part of the framework for example, you will need to include their namespaces: | ||
|
|
||
| ```yml | ||
| App\Test\Player: | ||
| john: | ||
| Name: join | ||
| App\Test\Team: | ||
| crusaders: | ||
| Name: Crusaders | ||
| Origin: Canterbury | ||
| Players: =>App\Test\Player.john | ||
| ``` | ||
|
|
||
| > [!WARNING] | ||
| > If your tests are failing and your database has table names that follow the fully qualified class names, you've probably forgotten to implement `private static $table_name = 'Player';` on your namespaced class. See [DataObject](api:SilverStripe\ORM\DataObject) for an example. | ||
|
|
||
| ## Defining many_many_extraFields | ||
| ## Defining `many_many_extraFields` |
There was a problem hiding this comment.
This is unrelated refactoring - but I noticed that this is actually outdated. All the above examples use namespaced classes.
I've moved the warning up above.
GuySartorelli
force-pushed
the
pulls/5/fixtures-in-custom-tables
branch
from
25ce8b4 to
8e794d1
Compare
michalkleiner
approved these changes
Mar 21, 2024
emteknetnz
approved these changes
Mar 27, 2024
emteknetnz
pushed a commit
to creative-commoners/developer-docs
that referenced
this pull request
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Documents how to create fixtures for tables that aren't backed by a
DataObjectclass.Issues
Pull request checklist