Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Composer: Use conflict and suggest properties #10

Closed
7 of 10 tasks
core23 opened this issue Apr 21, 2016 · 1 comment
Closed
7 of 10 tasks

Composer: Use conflict and suggest properties #10

core23 opened this issue Apr 21, 2016 · 1 comment
Labels
enhancement

Comments

@core23
Copy link
Member

core23 commented Apr 21, 2016 •
edited by VincentLanglet
Loading

As mentioned in sonata-project/SonataClassificationBundle#183, we should use the suggest property in the way it has been designed.

Some bundles use them as a normal required property, instead of leaving a message for this. The version information should be moved to the conflicts property.

Some bundles that I found so far:

  • SonataBlockBundle
  • SonataClassificationBundle
  • SonataDashboardBundle
  • SonataExporter
  • SonataMediaBundle
  • SonataNewsBundle
  • SonataNotificationBundle
  • SonataPageBundle
  • SonataSeoBundle
  • SonataUserBundle
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@core23 @VincentLanglet