Skip to content

Calling Firebase Cloud Functions directly from Dashboard#814

Merged
rolivares93 merged 12 commits intomainfrom
firekit-into-dashboard
Mar 6, 2026
Merged

Calling Firebase Cloud Functions directly from Dashboard#814
rolivares93 merged 12 commits intomainfrom
firekit-into-dashboard

Conversation

@rolivares93
Copy link

Proposed changes

I created a class called FirebaseService to handle cloud-function queries directly from the dashboard. It's just an initial thought, but this PR shows it working. I used a hard-coded mocking query, but if we keep this approach, we can place the queries into separate files as members of subclasses.

Screen.Recording.2026-02-27.at.16.24.53.mov

Types of changes

What types of changes does this pull request introduce?

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that does not add functionality but makes code cleaner or more efficient)
  • Tests (new or updated tests)
  • Styles (changes to code styling)
  • CI (continuous integration changes)
  • Other (please describe below)

Additional Notes

@digital-pro
Copy link
Collaborator

digital-pro commented Feb 27, 2026 via email

@github-actions
Copy link

github-actions bot commented Feb 27, 2026

Visit the preview URL for this PR (updated for commit 13c1911):

https://hs-levante-admin-dev--pr814-firekit-into-dashboa-7q8z1687.web.app

(expires Fri, 13 Mar 2026 15:12:28 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 7889bff1da3bcc333d7422b9fc863c65b3962be7

@digital-pro
Copy link
Collaborator

For example, we are creating non-dashboard tools that we want to have secure access for our partners (the audio approval tool for example). They need to use our auth system as they require the ability to read/write buckets and potentially firestore records. That is a must have capability.

@rolivares93 rolivares93 requested a review from asengupta3 March 4, 2026 14:48
@rolivares93
Copy link
Author

@digital-pro I just updated this PR and I left the auth as it is, so the non-dashboard tools will keep their access also as it is, ok?

@digital-pro
Copy link
Collaborator

digital-pro commented Mar 4, 2026 via email

families: a.families,
};
// Convert dates to Date objects, handling both timestamp strings and Date objects
const convertToDate = (dateValue) => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not directly related to this PR but can you move convertToDate out of here? It is a pure function and can be moved at the same place as getTitle.

Copy link
Collaborator

@asengupta3 asengupta3 left a comment

Choose a reason for hiding this comment

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

Looks good. Can you add to the REAME.md on how to use this new script and build a class and use it for a new set of functions? And also, how to add functions to a class.

@asengupta3
Copy link
Collaborator

@rolivares93 can you also update the title to Calling firebase functions directly or something similar? We are technically not adding Firekit to dashboard.

@rolivares93 rolivares93 changed the title Firekit into dashboard Calling Firebase Cloud Functions directly from Dashboard Mar 6, 2026
@rolivares93 rolivares93 requested a review from asengupta3 March 6, 2026 15:05
Copy link
Collaborator

@asengupta3 asengupta3 left a comment

Choose a reason for hiding this comment

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

This looks great! Thanks @rolivares93

@rolivares93 rolivares93 merged commit 5f6bc21 into main Mar 6, 2026
5 checks passed
@rolivares93 rolivares93 deleted the firekit-into-dashboard branch March 6, 2026 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants