diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-09 03:09:39 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-09 03:09:39 +0300 |
| commit | bc692af9882a4eb5b4b4ca6df682375f3a21cb44 (patch) | |
| tree | 8613106463a2cbfda58230a90505cc8ed661af55 /doc/development/packages.md | |
| parent | 66108e3b34cdba3eab53e07fdde76f799c0edc9b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/packages.md')
| -rw-r--r-- | doc/development/packages.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/packages.md b/doc/development/packages.md index 498fc2a83d9..11fc3faf4ab 100644 --- a/doc/development/packages.md +++ b/doc/development/packages.md @@ -196,8 +196,8 @@ information like the file `name`, `side`, `sha1`, etc. If there is specific data necessary to be stored for only one package system support, consider creating a separate metadata model. See `packages_maven_metadata` table -and `Packages::MavenMetadatum` model as an example for package specific data, and `packages_conan_file_metadata` table -and `Packages::ConanFileMetadatum` model as an example for package file specific data. +and `Packages::Maven::Metadatum` model as an example for package specific data, and `packages_conan_file_metadata` table +and `Packages::Conan::FileMetadatum` model as an example for package file specific data. If there is package specific behavior for a given package manager, add those methods to the metadata models and delegate from the package model. |