-
Notifications
You must be signed in to change notification settings - Fork 317
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
v1.3.0 #274
v1.3.0 #274
Conversation
|
Still want to test this out more, to make extra sure the list filter expressions and workflow changes are working, but reviewers can start taking a look. |
@cgreene I think this review is going to fall on you, as it's more of a philosophical design change than a technical change, aside from the one section of code that supports the Ruby expression filtering which is a little weird. I've also "annotated" the diff with comments that hopefully will make it easier to read. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Neat that you're using expressions for filters now. I left a few minor comments, but nothing that really needs to be addressed before merging.
Co-authored-by: Faisal Alquaddoomi <falquaddoomi@gmail.com>
Closes #272
Closes #269
Closes #191 (hopefully)
New template version checklist:
name
field for all debug/logging steps in workflowsjwalton/gh-find-current-pr
to get PR number to be more reliable (in rare cases,github.event.number
can be empty)description
gets appended touser
due to missing\n
in printf.yml
to.yaml
for consistencyif
skipping instead of job-level or workflow-level because of this issue.xml_escape
liquid filter wherever a user/third-party provided field is used in an HTML attribute to prevent special characters breaking HTML rendering. example:aria-label="{{ citation.title }}"
andcitation.title
is"Lorem Ipsum" dataset
, causing attribute to prematurely close.data_filter
to accept Ruby expressions instead of custom syntax. use Rubyeval
and define each field in the item as a local variable, e.g.{"animal": "cat"}
lets you usefilter="animal == 'cat'"
.<details>
element† due to a github limitation, it wouldn't not run anyway on the auto-created PR. the user must close/reopen the PR, then the regular "on pr" workflow (which includes running "build preview") will run. i've already updated the docs to talk about this. from now on, let's treat auto-opening PR as the only supported way. previously i considered that the user could change
open-pr
tofalse
to have "on schedule" commit updated citations directly tomain
, but let's nix that to maintain simplicity. it's probably better that we force the user to review the changes before pushing them to their live site anyway. if we did want to support that in the future, the "build preview" run i removed would have to be changed to a "build site", since we'd want to be re-building themain
branch version of the site, not a preview for a PR.