Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[L10n Tooling: i3] Re-implement download-from-glotpress logic from .py and .swift scripts #331
[L10n Tooling: i3] Re-implement download-from-glotpress logic from .py and .swift scripts #331
Changes from all commits
18fe0be
1e462e0
ca0a2f5
e3a2cb9
4b2fa32
8cc4438
e9cd88a
832343b
e89fe3a
dfe96a7
41225bf
c03b18d
3754e1e
b249b55
7e1dbea
9db104c
23d43b1
fd67884
ba0fdc6
e918ed0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This is the exception raised by
UI.user_error!
.PS: Note that we can't really use
allow(FastlaneCore::UI).to receive(:user_error!) { |m| … }
here because if we catch and stub those, that won't interrupt the action (i.e. the call here on L9 would not raise if stubbed so the rest of therun
method would continue executing).(And we could do
allow(FastlaneCore::UI).to receive(:user_error!) do |e| raise e }
to be sure that it still interrupts the code even when stubbed… but then what would be the point of stubbing the method while the real implementation already raises…)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.
Btw, wdyt of using a
lambda
like this here (which is basically the Ruby equivalent of an anonymous closure in Swift) so that it allowed me to still keep the# Act
and# Assert
separate?Is it readable and worth it? Or too obscure and you'd instead prefer to avoid the
lambda
and directly useexpect { run_described_fastlane_action(…) }.to …
… even if that means mixing the "Act" and "Assert" steps together and breaking the usual A/A/A structure of the tests just to be able to catch the exception raised by the "act" part?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.
I think it's a neat trick that doesn't affect the code readability much. Having said that, as much as I like AAA I think it would be okay to break the pattern here to keep the code concise.
Up to your preference.
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.
👍 I'll keep it then 🙂