Rush • A new and improved way of building extensions

[Shreyash (Shreyash Saitwal)]

Status update – I’ve officially restarted working on Rush. The next release will ship with a bunch of new exciting features like automatic dependency resolution and support for multi-component extensions among others.

There’s no concrete ETA because it’s been months since I last touched the codebase, but I hope to get this release ready for beta testing by the end of this month. Stay tuned!

[ashishthakoor58 (CYBEROXO)]

I am waiting for new update​

[JEWEL (Extension Developer 🧩)]

Feature request - Please add helper block feature using @Options and @OptionList annotations

[Taifun]

@JEWEL

Please add helper block feature using @Options and @OptionList annotations

@Shreyash what needs to be done to add these, see also

Need help to adding helper or drop down blocks in extension

Taifun

[zainulhassan]

Thats pretty cool. I would recommend using mason for generating project template. This way you would be able to separate template logic.

[Shreyash (Shreyash Saitwal)]

@Taifun

what needs to be done to add these

Rush does not support the helper blocks as of now. I haven’t started working on it yet since there’s already a lot on my plate, but they will be available as a part of the next release. If someone’s willing to contribute I’d really appreciate that.

[mahmoud_hooda (AEMO)]

Hello @Taifun
Like i told before rush doesn’t support that , there are problem to import this

import com.google.appinventor.components.common.OptionList;
import com.google.appinventor.components.common.Default;

[mahmoud_hooda (AEMO)]

@Shreyash

since there’s already a lot on my plate

We appreciate your effort, keep it up

[RDR_SA (Richard Roy)]

Hi, I am new to extension creation.
I am facing a problem when I try to build it.
Here the error

Here Other things

NOTE: I’m using VS code.
Please help me to solve it
Thank you

[Shreyash (Shreyash Saitwal)]

You have whitespace in your PC’s default username (IT SPACE) and Rush doesn’t quite get along with spaces in file paths. However, you can fix this yourself, read the below post:

Rush Build failed with internal error

Your %USERPROFILE% seems to have a whitespace in it. Do this: Copy/Move everything inside the %APPDATA%/rush directory to a place whose path has no whitespace, say, C:/rush . Then, create the RUSH_DATA_DIR environment variable and set its value equal to the path of the previous directory, in this case C:/rush. Build your extension with rush build .

[Shreyash (Shreyash Saitwal)]

@RDR_SA

NOTE: I’m using VS code.

This isn’t related to your issue but I’d suggest you use IntelliJ IDEA. VS Code fails to index extension libraries in Rush projects, bombarding you with all sorts of false errors. I want to fix this in a future update, but for now, it’s best to use IntelliJ (or Android Studio).

[RDR_SA (Richard Roy)]

After following this guide I have another issue.

[RDR_SA (Richard Roy)]

@Shreyash

it’s best to use IntelliJ (or Android Studio).

I already have android studio but I don’t know how to use rush on it.

[Shreyash (Shreyash Saitwal)]

You have JDK 18 on your PATH. Remove it, install JDK 8, and change JDK_HOME env var.

[RDR_SA (Richard Roy)]

@Shreyash

install JDK 8

Can you please share the download url.

[Anu10 (Anu)]

Rush • A new and improved way of building extensions

Try this version jdk - 1.8.0 https://www.oracle.com/in/java/technologies/javase/javase8u211-later-archive-downloads.html#license-lightbox first remove jdk bin path if there is any then install the jdk from above link install it and add bin path to system variable

[RDR_SA (Richard Roy)]

Currently

** Still have the same problem **

[Shreyash (Shreyash Saitwal)]

Make sure that you have restarted the terminal. If it still shows the same error, try building with the -r flag, this will invalidate the caches and build the extension afresh.

[RDR_SA (Richard Roy)]

After rush build -r

[Shreyash (Shreyash Saitwal)]

It looks like for some reason, Rush is still picking JDK 18 to compile your source files. Are you sure you restarted your terminal? If yes, can you try restarting your computer and then building with the -r flag again?