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

Add support for Akeneo 3.0 #18

Merged
merged 44 commits into from
Jun 27, 2019
Merged

Add support for Akeneo 3.0 #18

merged 44 commits into from
Jun 27, 2019

Conversation

AngelVazquezArroyo
Copy link
Contributor

No description provided.

Copy link
Collaborator

@flagbird flagbird left a comment

Choose a reason for hiding this comment

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

A first simple test of creating, editing and using the table attribute in a product worked. Export and import was able to create the table attribute values.

.travis.yml Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
src/Form/Extension/AttributeOptionTypeExtension.php Outdated Show resolved Hide resolved
src/Resources/config/doctrine.xml Show resolved Hide resolved
src/Resources/config/services.xml Show resolved Hide resolved
src/Validator/Constraints/TableValidator.php Outdated Show resolved Hide resolved
src/Normalizer/AttributeOptionNormalizer.php Show resolved Hide resolved
@AngelVazquezArroyo AngelVazquezArroyo force-pushed the 3.0 branch 4 times, most recently from 5d0e3f2 to deb32da Compare May 28, 2019 15:40
@AngelVazquezArroyo
Copy link
Contributor Author

  • Please be consistent in the Specs methods with the scope. Either use public or omit it. I personally prefer methods with scope
  • I created Tests need to be checked by static code analysis tools #27 for adding static analysis for tests, because adding it here would be out of scope
  • Spec method names have to be absolute: No "should", "could" or "maybe". Do or do not. There is no try. The names will be used in the output of failing tests.

@flagbird This PR is ready again fora new review.

Copy link
Collaborator

@flagbird flagbird left a comment

Choose a reason for hiding this comment

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

This PR is ready again fora new review.

Not all of the previous changes were done. This PR is not ready for another review.

Here are additional changes:

@AngelVazquezArroyo
Copy link
Contributor Author

@flagbird PR is ready to be again reviewed.

Copy link
Collaborator

@flagbird flagbird left a comment

Choose a reason for hiding this comment

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

This should be sufficiant for a first 3.0 Release.

More details on coding style for tests and specs can be done in #27.

Copy link
Contributor

@amansilla amansilla left a comment

Choose a reason for hiding this comment

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

Thanks for the huge effort guys!

@amansilla amansilla merged commit db270ff into master Jun 27, 2019
@amansilla amansilla deleted the 3.0 branch June 27, 2019 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review Needs code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants