Open
Description
Background
Barrelsby should be used solely while developing, thus compiled barrels should be present while creating PRs.
Proposal
To validate this process, add a --check
flag that will not output to the filesystem. Instead, it will compare the desired outputs with the current file system and exit with a non-zero code if there is such a difference. Desirable with some details about which files weren't added during the development phase.
Metadata
Metadata
Assignees
Labels
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
adamgen commentedon Mar 13, 2022
As a walkaround, I'm running this in my CI to check if there are changed files after running barrelsby.
github-actions commentedon Jun 12, 2022
No activity has been seen recently, marking as stale. If this is a mistake please reach out to a collaborator
adamgen commentedon Jul 3, 2022
Inspired by the integration-tests script I think that a simple implementation for it would be to:
.barrelsby-index.check.ts
..barrelsby-index.check.ts
with the ordinaryindex.ts
while ignoring whitespaces..barrelsby-index.check.ts
files.@BitForger, @bencoveney does this sound like a bad idea?
BitForger commentedon Aug 7, 2022
Sorry, as you can tell we've both been pretty busy with the personal lives.
My idea for implementation would probably be to walk through and do everything up until the point of creating the file and just compare the contents of the existing file with the string we created in memory. If it matches we exit 0 and if not we exit 1 with the differences if that isn't too hard to do.
github-actions commentedon Dec 5, 2022
No activity has been seen recently, marking as stale. If this is a mistake please reach out to a collaborator
github-actions commentedon Apr 13, 2023
No activity has been seen recently, marking as stale. If this is a mistake please reach out to a collaborator