-
Notifications
You must be signed in to change notification settings - Fork 919
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
Add new command for discoverying function triggers. #5213
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
Codecov ReportBase: 56.36% // Head: 56.33% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #5213 +/- ##
==========================================
- Coverage 56.36% 56.33% -0.04%
==========================================
Files 313 313
Lines 21056 21066 +10
Branches 4278 4278
==========================================
- Hits 11869 11868 -1
- Misses 8161 8172 +11
Partials 1026 1026
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
0b62447
to
0d6179a
Compare
I would take the side of running this through API council since it has to be public facing and they might have naming suggestions for internal only commands. Alternatively, I think we should at least get @bkendall's sign-off as the CLI TL before merging this |
@colerogers Since @bkendall won't be back for some time, I'll go ahead and draft an API proposal. |
src/commands/functions-discover.ts
Outdated
const builds = await loadCodebases(fnConfig, options, firebaseConfig, { | ||
firebase: firebaseConfig, | ||
}); | ||
logger.info(JSON.stringify(builds, null, 2)); |
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.
Should this JSON.stringify
be try/catch'd ?
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 feel like that edge case is rare enough, and we can rely on the CLI's global try-catch mechanism. We are going to rethrow the error anyway right?
WDYT?
6ac68b8
to
68889a4
Compare
68889a4
to
8144450
Compare
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.
🔥
19cb747
to
0078352
Compare
eecb3dc
to
15e23ca
Compare
Graphite Merge Job Current status: ✅ Merged This pull request was successfully merged as part of a stack. This comment was auto-generated by Graphite. Job Reference: Uhty8UE38l3MKEIRA9gp |
Adds an internal CLI command for discovering function triggers in a given project directory:
I intend to use the command to wire up integration test for discovery portion of a function deployment in the follow up PR.
This PR makes a small refactoring of the function deployment code to extract out the pieces for discovering functions. I verified that the function deploy integration test still passes after this refactor (Test Run).
DO NOT MERGE: New command requires an internal API proposal approval.