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
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
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