Skip to content
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

importing projects workflow tech debt #4185

Open
johrstrom opened this issue Feb 26, 2025 · 0 comments
Open

importing projects workflow tech debt #4185

johrstrom opened this issue Feb 26, 2025 · 0 comments

Comments

@johrstrom
Copy link
Contributor

While looking at #4178 I think we need to clean this up a bit after we merge.

I'm thinking importing a project should likely route to new_projects_path (i.e, projects_controller#new ) with a POST parameter saying it's an import (like how templates work). This will reduce the amount of routes we have, thereby cleaning it all up a little.

how that'll affect the views, I'm not entirely sure but I feel like importing a project is logically very close to creating a new project (from scratch or from a template).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants