Skip to content

Fe overhaul managed compute and onboarding #1614

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

Merged
merged 118 commits into from
Apr 29, 2025

Conversation

grutt
Copy link
Contributor

@grutt grutt commented Apr 24, 2025

Description

Adds onboarding and managed compute

@@ -0,0 +1,29 @@
name: Sync Go Quickstart

Copy link
Contributor

Choose a reason for hiding this comment

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

Can we have a single action for these that loops through the three or something? looks like these are all the same

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the on paths is different for each, i wanted one too but i dont want to push changes to all if only 1 changes

Copy link
Contributor

Choose a reason for hiding this comment

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

womp womp

value={selectedWorkflowId}
onChange={(e) => {
setSelectedWorkflowId(e.target.value);
setSelectedRunId(''); // Reset selected run when workflow changes
Copy link
Contributor

Choose a reason for hiding this comment

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

nit but something I really dislike about the AI-gen code 😅 I really dislike comments like this - it's obvious if you're reading the code what's going on here, and if it's not that's a problem with how the code is written IMO

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah, i agree

{!disabledCapabilities.includes('workflow') && (
<div>
<label className="text-sm font-medium">Workflow</label>
<select
Copy link
Contributor

Choose a reason for hiding this comment

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

should we be using shad components here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good catch

unknown: 'txt',
};

// This is a server component that will be rendered at build time
Copy link
Contributor

Choose a reason for hiding this comment

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

do we have server components?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

its statically rendered at build time, maybe its not technically a server component

const currentStepIndex = activeStep ? stepKeys.indexOf(activeStep) : -1;

useEffect(() => {
console.log('activeStep', activeStep);
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm surprised these log lines aren't caught by the linter?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

me too

Copy link
Contributor

@mrkaye97 mrkaye97 left a comment

Choose a reason for hiding this comment

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

left a couple comments but basically blindly approving 😅 tough to really review this

I have some qualms with the vibe coded stuff but I think it's fine to leave for now :P

@grutt grutt merged commit 17fe456 into fe-overhaul Apr 29, 2025
34 of 39 checks passed
@grutt grutt deleted the fe--overhaul-managed-compute branch April 29, 2025 13:35
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