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

Torq IT New Additions #382

Closed
wants to merge 42 commits into from

Conversation

jeremygnoonan
Copy link

@jeremygnoonan jeremygnoonan commented Dec 5, 2023

As discussed with @fashxp regarding a number of new features to the data importer. Had started a private extensions repo @ Torq but then decided to connect with Pimcore and see if any of it was interest to pull into the main repo.

Did my best to update the docs, so a good place to reference everything that has changed.
Highlights:

  • Added Symfony Expression filter to all file formats
  • Added the Composed Parent and Composed Path resolvers (my favourite addition)
  • Added a Composed Path Asset Loader (related to above)
  • Replaced the Excel parser with Openspout. This has worked well for me. open for input on if we see risk here. MUCH more memory friendly.
  • Added the option to Bulk Load excel files to queue table (just dawned on me that this could easily be done for all file formats). SUPER fast for large files, can queue 100K+ records in seconds.
  • Added a loading strategy based on the value of a property
  • Added a transformation to make a string safe for a Pimcore key
  • Added a transformation to return a constant value (useful to assign something as a variant)
  • Added a data target that allows adding an image to the end of an image gallery.
  • Added a data target that allows setting a property
  • Added the overwrite options from Direct into Classification Store DataTarget

Submitting this as draft as I want to do some additional testing, but also wanted to give visibility.

jeremygnoonan and others added 30 commits November 8, 2023 09:31
Copy link

github-actions bot commented Dec 5, 2023

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@jeremygnoonan
Copy link
Author

recheck

@jeremygnoonan jeremygnoonan marked this pull request as ready for review December 7, 2023 14:49
@herbertroth
Copy link
Member

Can you please merge or rebase the changes from 1.x to your PR? This is mostly for using qodana to check the PR.

@jeremygnoonan
Copy link
Author

Can you please merge or rebase the changes from 1.x to your PR? This is mostly for using qodana to check the PR.

Done

@jeremygnoonan
Copy link
Author

@herbertroth can you point me in the correct direction to sign the CLA? I am not getting a prompt here like the main Pimcore repo.

@herbertroth
Copy link
Member

You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

@herbertroth
Copy link
Member

I have read the CLA Document and I hereby sign the CLA

@herbertroth
Copy link
Member

recheck

@herbertroth
Copy link
Member

@jeremygnoonan Sorry, there was a problem with the allowlist in our cla check. github-actions[bot] was not in this list. So please rebase again...

@jeremygnoonan
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

@jeremygnoonan
Copy link
Author

@herbertroth done

@herbertroth
Copy link
Member

@jeremygnoonan Sorry, sorry, sorry... pleas rebase again...

@mcop1 mcop1 added this to the 1.9.0 milestone Dec 18, 2023
@alexz707
Copy link

Hi Jeremy,

First and foremost, thank you so much for your extensive contribution to our project!
We truly appreciate the time and effort you've invested in enhancing the codebase with numerous features and bug fixes.

After reviewing your pull request, it appears that it contains some breaking changes, such as the addition of a method to an interface and typed properties to existing ones.
While we value the improvements you've made, we've found that the PR is quite comprehensive, and handling such a large set of changes can be challenging.
Given the wide range of the changes, it would be beneficial for us to work through them in smaller, more manageable pieces.

Before you embark on the task of splitting the PR, we suggest reaching out to our enterprise support team.
They can provide valuable insights into which features would be best to start with and guide you through the process.
Collaborating with them at this stage will help ensure a smoother review and integration process.

Once again, thank you for your dedication to improving our project.
We look forward to working together to make the integration process as seamless as possible.

Best regards,
Alex

@alexz707 alexz707 closed this Dec 21, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Dec 21, 2023
@fashxp fashxp removed this from the 1.9.0 milestone Feb 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants