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

feat: JS and templated URL management in one input #442

Open
atopper opened this issue Oct 23, 2024 · 2 comments
Open

feat: JS and templated URL management in one input #442

atopper opened this issue Oct 23, 2024 · 2 comments
Assignees

Comments

@atopper
Copy link
Collaborator

atopper commented Oct 23, 2024

Many users create unique import JS for specific templates such as 'blogs', 'news', 'events', etc. They keep a list of those URLs in files and then copy/paste them into the URLs field and then change the Transformation file URL field to match those templates (i.e. blog.import.js, or news.import.js).
That is awkward.

Expected Behaviour

Matching the list of URLs (templates) to the JS script could be done many ways. For example:

FUTURE

  • Could crawling help set up the TXT files?

Actual Behaviour

There is a lot of copy/pasting and manual typing and awkwardness when managing/matching URLs and scripts.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

atopper added a commit to atopper/helix-importer-ui that referenced this issue Oct 24, 2024
@kailasnadh790
Copy link

The current process of manually managing and matching URLs with transformation scripts is indeed cumbersome, especially for users handling multiple templates like blogs, news, and events. Automating the process through a "Load URLs" button that reads from a text file would streamline workflows significantly, reducing copy-pasting and potential for errors. This enhancement would make the feature more efficient and user-friendly, especially for bulk imports. Additionally, exploring future options like automated crawling for URL generation could be a valuable improvement to this functionality.

Also, currently in Helix Importer, we keep losing the URLs that we import as they are not saved anywhere. This approach would help in addressing that issue.

+1 for implementing this feature!

@atopper atopper self-assigned this Nov 7, 2024
@atopper
Copy link
Collaborator Author

atopper commented Nov 7, 2024

It would look a little like this quickly created video (no audio - basic idea) below.

If you want to try it out, do this command with a fairly recent recent aem-cli npm installation - version 16.7.11 or more recent:
aem import --ui-repo=https://github.com/atopper/helix-importer-ui#442-url-management
If you'd like to see this in the main product, please let a comment in this issue. Thanks.

url_templates.mp4

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

No branches or pull requests

2 participants