12/13/2022 0 Comments Gitify resources![]() ![]() Dealing with ClosuresĪ Closure is a separate table in the database that a core or third party extra may use to keep information about a hierarchy in a convenient format. For clarify, it can't hurt to add it to each data entry that uses it. gitify file to load ContentBlocks Layouts & Fields: data:Īs it'll load the package into memory, it's only required to add the package once. For example, you could use the following in your. core_path setting suffixed with model/, ]components//model/or a hardcoded package_path property. This will run $modx->addPackage before attempting to load the data. When a certain class is not part of the core models, you can define a package as well. When using GitifyWatch, there is also an environments root node in the gitify file, refer to the GitifyWatch documentation for more about that. This contains an array which can be turned into a valid xPDO criteria. This can help with syntax highlighting in IDEs.Įach partition can also specify a where property. yaml extension, but if you want you can override that with a extension property. The primary is used for the file names and is also related to the automatic ID conflict resolution.īy default files will be created with a. This defaults to id, but in many cases you may want to use the name as that is more human friendly. ![]() The primary field determines the key to use in the name of the generated files. Each partition specifies either a type that has special processing going on (only content is available as type currently), or a class which specified the xPDOObject derivative that you want to use. These partitions are basically the name of the directory that holds all the files of that type, and can also be used in the Gitify extract and Gitify build commands. There are root nodes for data_directory (the relative path where to store the files), backup_directory, data and packages.ĭata contains an array of what we call "Partitions". gitify may look like this: data_directory: _data/Ĭlass: modFormCustomizationProfileUserGroup This file is located in the root of the project.Īn example. To define what to export, to where and how, we're using a. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |