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

First phase of react-native-ide to radon IDE renaming - renaming non-visible bits first #538

Merged
merged 2 commits into from
Sep 13, 2024

Conversation

kmagiera
Copy link
Member

@kmagiera kmagiera commented Sep 12, 2024

This is the first step for our renaming process. It renames most react-native-ide occurences that doesn't affect users or are not visible.

  1. We're republishing react-native-ide under radon-ide package name (next step would be to fallback from react-native-ide to radon-ide)
  2. We are adding new configuration scheme "radon-ide" but for now keeping it as a copy. We want to accept new and old schemes going forwards and deprecate the old one after renaming is complete.
  3. We're keeping all user-facing name as-is for the time being. Will want to update docs first for the transition to complete – those changes will come as a follow up.
  4. Code changes are mostly made to be backwards compatible and when possible we are supporting old names (i.e. for NPM package or for the config scheme)

Final tricky part is caches file location. Since it contains android emulator configs that in turn contain absolute path names we may need to consider dropping caches entirely with the update (haven't decided on this one yet).

Test plan

  1. Full test over expo-router app. It also uses custom config along with preview functionality

Copy link

vercel bot commented Sep 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-native-ide ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 13, 2024 9:19am

Copy link
Collaborator

@filip131311 filip131311 left a comment

Choose a reason for hiding this comment

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

Left some inline comments, please take a look at them before merging

"description": "Provides a way to customize Gradle builds for Android",
"type": "object",
"properties": {
"variant": {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Those are incorrect properties, android launch configuration takes two values, buildType and productFlavor

Copy link
Member Author

Choose a reason for hiding this comment

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

I just copied schema from the config we currently use. I can change that in both places then

@@ -25,7 +25,9 @@ export class LaunchConfigController implements Disposable, LaunchConfig {

const configurations = launchConfiguration.get<Array<Record<string, any>>>("configurations")!;

const RNIDEConfiguration = configurations.find(({ type }) => type === "react-native-ide");
const RNIDEConfiguration = configurations.find(
({ type }) => type === "react-native-ide" || type === "radon-ide" // for compatibility we want to support old configuration type name
Copy link
Collaborator

Choose a reason for hiding this comment

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

This solution will give a first instance of a configuration, so if someone has two configurations at the same time they will get a random one, I believe we should put a priority on "radon-ide" configurations.

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't intent to keep them both actually. The plan is that in the follow up version we will be displaying messages if someone is using the old config asking to rename it. Would prefer to avoid adding complexity to handle a usecase that seem to be very unlikely

@kmagiera kmagiera merged commit f126d51 into main Sep 13, 2024
3 checks passed
@kmagiera kmagiera deleted the kmagiera/renaming-phase1 branch September 13, 2024 09:50
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.

2 participants