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.

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

EZP-30627: Unified Twig helpers naming #2663

Merged
merged 4 commits into from
Jun 25, 2019
Merged

EZP-30627: Unified Twig helpers naming #2663

merged 4 commits into from
Jun 25, 2019

Conversation

pawbuj
Copy link
Contributor

@pawbuj pawbuj commented Jun 6, 2019

Question Answer
JIRA issue EZP-30627
Bug/Improvement yes
New feature no
Target version master
BC breaks yes
Tests pass yes
Doc needed yes

related to : ezsystems/ezplatform-admin-ui#1008

TODO:

  • Implement feature / fix a bug.
  • Implement tests.
  • Fix new code according to Coding Standards ($ composer fix-cs).
  • Ask for Code Review.

@gggeek
Copy link
Contributor

gggeek commented Jun 7, 2019

Following up the discussion at #2633 : were the current names of twig helpers already declared as deprecated? If not, I'd politely suggest to keep around the old name (and add a deprecation notice for any usage) for at least the duration of one major kernel version. Twig helpers tend to be one of the apis most used by every ez developer...

@emodric
Copy link
Contributor

emodric commented Jun 7, 2019

I fully agree with @gggeek and his sentiment expressed in #2663. And is also valid for #2658 .

@alongosz alongosz added this to the 8.x milestone Jun 19, 2019
@alongosz alongosz changed the title EZP-30627: Unify twig helpers naming EZP-30627: Unified twig helpers naming Jun 24, 2019
*
* @return string|null
*/
public function getTranslatedProperty(ValueObject $object, $property, $forcedLanguage = null)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you drop it? Seems out of scope.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because I dropped ez_trans_prop

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because I dropped ez_trans_prop

Not following, scope was to unify naming, not drop features. Is there a replacement for this one?

@@ -39,6 +39,6 @@ public function getName()
*/
public function getGlobals()
{
return array('ezpublish' => $this->globalHelper);
return ['ez_app' => $this->globalHelper];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather ezplatform, it's about the Product.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Symfony provides app global helper , ezPlatform provides ez_app . So, it is because of naming compatibility with symfony.

Copy link
Member

@alongosz alongosz Jun 25, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still -1 from my side.
// Edit as to why:
We have product, not project. Moreover if we wanted to distinguish configuration of eZ Platform and e.g. eZ Commerce, we couldn't follow any convention with such naming.
On top of that, it's also about Product placement.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In most cases (with exceptions of course, but this is not the case here) renaming ezpublish to ezplatform is recommended.

@alongosz alongosz changed the title EZP-30627: Unified twig helpers naming EZP-30627: Unified Twig helpers naming Jun 24, 2019
@lserwatka
Copy link
Member

Due to large amount of changes for Symfony 4 and cleanup around templates directory structures, this change does not add any significant work which needs to be done during upgrade anyway, especially that we are considering to provide a simple bash/PHP command or entire compatibly bundle. Subject is still open.

@alongosz
Copy link
Member

@pawbuj besides my previous review please list those changes in /doc/bc/changes-8.0.md so it's easy to find them for anyone upgrading.

@lserwatka lserwatka merged commit 90226b9 into master Jun 25, 2019
@lserwatka lserwatka deleted the EZP-30627 branch June 25, 2019 13:01
@MarioBlazek
Copy link
Contributor

@lserwatka does it mean that the next version of eZ Platform is going to be 100% Symfony 4/5 compliant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

8 participants