| @@ -67,10 +67,11 @@ Follow the following steps to update documentations to their latest version: · 66 unmodified lines |
| 67 | 2. Check if the license is still correct. If you update `options[:attribution]`, also update the documentation's entry in the array in [`assets/javascripts/templates/pages/about_tmpl.coffee`](../assets/javascripts/templates/pages/about_tmpl.coffee) to match. | 67 | 2. Check if the license is still correct. If you update `options[:attribution]`, also update the documentation's entry in the array in [`assets/javascripts/templates/pages/about_tmpl.coffee`](../assets/javascripts/templates/pages/about_tmpl.coffee) to match. |
| 68 | 3. If the documentation has a custom icon, ensure the icons in <code>public/icons/*your_scraper_name*/</code> are up-to-date. If you pull the updated icon from a place different than the one specified in the `SOURCE` file, make sure to replace the old link with the new one. | 68 | 3. If the documentation has a custom icon, ensure the icons in <code>public/icons/*your_scraper_name*/</code> are up-to-date. If you pull the updated icon from a place different than the one specified in the `SOURCE` file, make sure to replace the old link with the new one. |
| 69 | 4. If `self.links` is defined, check if the urls are still correct. | 69 | 4. If `self.links` is defined, check if the urls are still correct. |
| 70 | 5. Generate the docs using `thor docs:generate <doc@version>`. | 70 | 5. If the scraper inherits from `FileScraper` rather than `URLScraper`, follow the instructions for that scraper in [`file-scrapers.md`](../docs/file-scrapers.md) to obtain the source material for the scraper. |
| 71 | 6. Make sure `thor docs:generate` doesn't show errors and that the documentation still works well. Verify locally that everything works and that the categorization of entries is still good. Often, updates will require code changes in the scraper or its filters to tweak some new markup in the source website or to categorize new entries. | 71 | 6. Generate the docs using `thor docs:generate <doc@version>`. |
| 72 | 7. Repeat steps 5 and 6 for all versions that you updated. | 72 | 7. Make sure `thor docs:generate` doesn't show errors and that the documentation still works well. Verify locally that everything works and that the categorization of entries is still good. Often, updates will require code changes in the scraper or its filters to tweak some new markup in the source website or to categorize new entries. |
| 73 | 8. Create a PR and make sure to fill the checklist in section B of the PR template (remove the other sections). | 73 | 8. Repeat steps 5 and 6 for all versions that you updated. |
| | 74 | 9. Create a PR and make sure to fill the checklist in section B of the PR template (remove the other sections). |
| 74 | | 75 | |
| 75 | ## Coding conventions | 76 | ## Coding conventions |
| 76 | | 77 | |