Skip to content

Introduce "title" property to schema #1141

Closed
wants to merge 1 commit into from

4 participants

@kdambekalns

Introduce a new property "title" which can contain a concise human-readable
title for the package. Backwards compatibility: If a "title" property exists,
it is used as a label in listings. If it's empty, the package name could be
used as a fallback. But in the end it's up to the application which
information is displayed.

Fixes: #1140

@kdambekalns kdambekalns Introduce "title" property to schema
Introduce a new property "title" which can contain a concise human-readable
title for the package. Backwards compatibility: If a "title" property exists,
it is used as a label in listings. If it's empty, the package name could be
used as a fallback. But in the end it's up to the application which
information is displayed.

Fixes: #1140
a3d4289
@stof
stof commented Sep 24, 2012

This does not fix the related ticket entirely. The schema allows the property but it is totally unused, meaning Packagist will not be able to know its value for instance

@naderman
Composer member
naderman commented Oct 5, 2012

@kdambekalns To clarify you need to add loading of this value to the Package code in composer that is used by Packagist. E.g. https://github.com/composer/composer/blob/master/src/Composer/Package/CompletePackage.php should provide a way to access the title. And the loaders in https://github.com/composer/composer/tree/master/src/Composer/Package/Loader need to be able to load the title.

@stof
stof commented Oct 5, 2012

And the dumper needs to dump it again

@Seldaek
Composer member
Seldaek commented Mar 4, 2013

Closing in favor of #1648

@Seldaek Seldaek closed this Mar 4, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.