Json backlog testing#1878
Conversation
✅ Deploy Preview for cyf-curriculum ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-common ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
illicitonion
left a comment
illicitonion
left a comment
There was a problem hiding this comment.
LGTM!
Presumably at some point we'll inline the issue text (so we don't have issue URLs any more), and do some auto-magic around generating e.g. the "how to submit" text rather than having it inline in each issue? (But before doing that, we either need to update the issue cloner to create issues from our source of truth rather than issues, or need to stop using coursework planners like we are)
| */}} | ||
| {{ range $repos }} | ||
| {{ $issueBlocks := partial "block/issues-list-as-blocks.html" (dict "backlog" . "backlog_filter" $backlog_filter "path" $currentPath) }} | ||
| {{ if eq 0 ($issueBlocks | len)}} |
There was a problem hiding this comment.
This is great for testing partial progress, but let's turn it into an error before merging
| {{ $courseRegex := `/(.*?)/` }} | ||
| {{ $courseName := (trim (index (findRE $courseRegex .path 1) 0) "/") }} |
There was a problem hiding this comment.
I think .Page.Section is the name of the course without needing to do path regex
2 participants
DRAFT - Testing an alternative way of storing backlog issues
org-cyf/data/backlog.jsonwith title, category and url of current backlog issuesissues-list-as-blocks.htmlto load the list of issues from this file instead of using the GitHub APIbacklog.html,backlog-issue.htmlandblock.htmlto reflect the different data structurebacklog/index.mdfor each ITP/SDC module to update labelssuccess.mdto display backlog titles correctly. Note: this means workshop titles do not display correctly. Leaving this for now while work is ongoing on Merge workshop content into currlicum #1822, I'll revisit once we have all the workshops in the same format.Currently this works with a copy of the JSON generated by #1841. If a module wasn't included in that then it won't work here.