Skip to content

chore(site): remove create template xservice #10112

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 17 commits into from
Oct 9, 2023

Conversation

BrunoQuaresma
Copy link
Collaborator

In the process of removing the create template service, I split the page into three views to represent each possible action:

  • Duplicate an existing template
  • Upload a .tar
  • Import from a starter template

I think with this, things are easier to reason about.

PS: I tried my best not to create deep abstractions so for now, I would rather have more duplicate code - but easier to understand - than very low code that is hard to change later.

Related to: #9940

@BrunoQuaresma BrunoQuaresma requested a review from aslilac October 6, 2023 17:04
@BrunoQuaresma BrunoQuaresma self-assigned this Oct 6, 2023
Comment on lines +163 to +172
export class JobError extends Error {
public job: ProvisionerJob;
public version: TemplateVersion;

constructor(job: ProvisionerJob, version: TemplateVersion) {
super(job.error);
this.job = job;
this.version = version;
}
}
Copy link
Member

Choose a reason for hiding this comment

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

do we have somewhere more general we can put these sorts of errors? not crazy about this being tucked away in queries/

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We don't but I'm open to it if you have any place or organization in mind.

Copy link
Member

Choose a reason for hiding this comment

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

maybe util/errors or something? I don’t tend to like util/ folders, but it’d be slightly more reusable there until we think of somewhere better

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hm... Idk but I feel it is kinda of far from where it is used since it is only used there - for now and probably it will be the only place where it makes sense IMO.

@BrunoQuaresma BrunoQuaresma merged commit 584a2e8 into main Oct 9, 2023
@BrunoQuaresma BrunoQuaresma deleted the bq/refactor-create-template branch October 9, 2023 17:10
@github-actions github-actions bot locked and limited conversation to collaborators Oct 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants