Closed mueschm closed 1 year ago
@mueschm @ryan-cahill For UX perspective, I get an experimental warning we should suppress - looks a little janky when we run init:
architect init //Tue Mar 21 08:15 AM// ✔
? What is the name of your project? (node:19772) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Beyond that experimental warning, everything looks great from a UX perspective. I tested a bunch of bad project names and I love how the UX looks for it.
Once the experimental warning is fixed, you have prod signoff
@mueschm @ryan-cahill For UX perspective, I get an experimental warning we should suppress - looks a little janky when we run init:
architect init //Tue Mar 21 08:15 AM// ✔ ? What is the name of your project? (node:19772) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time (Use `node --trace-warnings ...` to show where the warning was created)
I don't see how this pr would have introduced that warning. @Zach-at-Arch can you try running architect init on rc and see if you get the same warning? If you do then create a separate cli ticket.
@tjhiggins yep, it's on RC as well. I'll make a ticket; therefore, this is good to go
:tada: This PR is included in version 1.36.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Overview
When trying to create a new project with a
docker-compose.yml
in the current working directory, there was no good mechanism to use a starter project. This PR fixes that core issue and streamlines some of the code.Changes
Tests
Pictures