这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@Jpoliachik
Copy link
Contributor

Please verify the following:

  • yarn test jest tests pass with new tests, if relevant
  • README.md has been updated with your changes, if relevant

Describe your PR

  • Adds an extra step in the decision tree for ignite-cli new: Do you want to use Expo?
  • Adds cng workflow type to replace prebuild, to match Expo's naming. Deprecated prebuild for potential future removal.

Note: References new Ignite Cookbook recipe from infinitered/ignite-cookbook#116

Screenshots

image image

@markrickert markrickert self-requested a review January 11, 2024 17:00
Copy link
Member

@markrickert markrickert left a comment

Choose a reason for hiding this comment

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

Nice! LGTM

@Jpoliachik Jpoliachik changed the title feat: split expo workflow decision tree, use 'cng' instead of 'prebuild' feat(cli): split expo workflow decision tree, use 'cng' instead of 'prebuild' Jan 11, 2024
@joshuayoes
Copy link
Contributor

up

1 similar comment
@jamonholmgren
Copy link
Member

up

@GantMan
Copy link
Member

GantMan commented Jan 12, 2024

UP!

@morganick
Copy link
Contributor

I need this!

@joshuayoes
Copy link
Contributor

hi mark

@Jpoliachik
Copy link
Contributor Author

I'm flattered by the suspiciously sudden interest in this

@jonmajorc
Copy link

so... where we at with this?

Copy link
Contributor

@frankcalise frankcalise left a comment

Choose a reason for hiding this comment

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

I think this looks good, nice work!

I'm only questioning if we should change the wording for "Do you want to use Expo" for a couple reasons

One, using Expo means many things (cli, SDK, EAS, etc)
Two, each workflow we're using Expo CLI and SDK here out of the box with Ignite so it seems misleading to ask it if on the DIY option it's not actually undoing those

I'm trying to think of what would read better, though.

@Jpoliachik
Copy link
Contributor Author

@frankcalise I see what you mean, how it could be ambiguous to ask "do you want to use Expo" - since we also technically use Expo libraries in DIY flow, and EAS - but IMO I think its suitable enough to help users simply decide "do I want to buy into the whole Expo ecosystem or not".

I'm going to go ahead and merge, but I'm happy to revise if we think of something better in the future.

@Jpoliachik Jpoliachik merged commit 1b40712 into master Jan 12, 2024
@Jpoliachik Jpoliachik deleted the feat/expo-decision-tree branch January 12, 2024 20:16
@jamonholmgren
Copy link
Member

Hmm...why didn't this land? 🤔

@jamonholmgren
Copy link
Member

@joshuayoes
Copy link
Contributor

@jamonholmgren
Copy link
Member

Regenerated it. Re-running.

@jamonholmgren
Copy link
Member

Hmm, maybe I need to delete the expired one. Re-running again.

infinitered-circleci pushed a commit that referenced this pull request Jan 15, 2024
# [9.4.0](v9.3.1...v9.4.0) (2024-01-15)

### Features

* **cli:** add expo decision tree, use 'cng' to replace 'prebuild' ([#2607](#2607) by @Jpoliachik) ([1b40712](1b40712))
@infinitered-circleci
Copy link
Collaborator

🎉 This PR is included in version 9.4.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants