Skip to content

Conversation

@midzer
Copy link
Contributor

@midzer midzer commented Jul 21, 2024

(Trying) to fix #545

@parkr parkr requested a review from ashmaroli July 21, 2024 18:50
Copy link
Member

@parkr parkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One looks right to me but the other needs another look. Thanks for playing along!

@ashmaroli
Copy link
Member

and both ways appear to match desired file names.

@midzer :) the thing is that both forms are 99% equivalent. The gotcha with Ruby compared to Python is that one can have multiple ways to implement the same idea. Therefore, if something; next item; end is almost equivalent to next item if something.

What Parker highlighted in his explanation is that creating the array [".", ".."] for each iteration is waste of resources, albeit hardly noticeable in most situations. To that end, your suggestion to use Dir.each_child is indeed a superior alternative. It's just that we would have to be certain that subdirectories are handled properly as well (Disclaimer: I'm not totally familiar with the pebble platform or the importer code).

@ashmaroli ashmaroli changed the title fix Pebble Regression Fix erroneous cosmetic changes in Pebble importer Jul 23, 2024
@ashmaroli
Copy link
Member

LGTM!

@jekyllbot: merge +dev

@jekyllbot jekyllbot merged commit a8a04c2 into jekyll:master Jul 23, 2024
jekyllbot added a commit that referenced this pull request Jul 23, 2024
github-actions bot pushed a commit that referenced this pull request Jul 23, 2024
midzer: Fix erroneous cosmetic changes in Pebble importer (#546)

Merge pull request 546
@ashmaroli
Copy link
Member

Thank you @midzer. :)

@jekyll jekyll locked and limited conversation to collaborators Jul 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants