37mediagroup I think the weakness in your approach is relying on a linter for validation. As you may be aware, the software I wrote not only performs a lint function, but, it also validates a feed file for any logic errors (ie. missing required fields, etc.). Additionally, I use the following methodology when making changes to a feed file.
Prerequisite: I created an identical test (private) channel for testing changes to my feed file. This uses a separate feed file which is a copy of the production feed.
- Open my test feed and make any changes.
- Submit the test feed and preview the changes on my Roku. If necessary, make changes to the test feed file and repeat.
- Once I am satisfied with the changes to the test feed file, I make a copy of the test feed and name it the same as my production feed. I then upload the production feed to my server while preserving its original name.
The above procedure was, at one time, very quick. However, something changed in the way Roku processes test channels. Prior to the change, updates to a test file were instant. Now, they are subject to the same refresh requirements as a production channel. I've complained about the time lapse for test channels, but, it fell on deaf ears.
