Hi Shreyash, here is a bug. When I type the command to create extension, this alert message appears even when I am in different directory. I got this bug first trying to create extension with same name with different folder when I got this alert message and now I am in different directory but still the warning appears.
edit: solved by removing space 
. But I remember it working with space
Nope, it's not a bug. Extension name can't contain spaces.
Yes, you'll have to add it to the AndroidManifest.xml.
Rush 1.1.0
Building extensions is now almost 1.5x faster with Rush! Yes, you heard that right, 1.5x faster than previous versions! Don't believe me, give it a shot yourself and feel the speed. 
Want to port your old extension(s) to Rush but fear rewriting those huge manifest annotations? No worries, I got your back. Introducing the migrate command! 
Simply run rush migrate in your extension template's root directory and let Rush do the rest of the work. Learn more here.
You can now install Rush using the Rush installer -- rush-init. It's not a full-blown installer and yeah, there's still a lot of room for improvement, but hey, it's better than nothing.
The notorious "no extension in the out directory" bug is finally fixed (hopefully). 
Some Android manifest tags weren't being added to the application's AndroidManifest.xml when using Kodular. This issue is now fixed and you should be able to use all the supported manifest elements without any headache.
Previously, aliasing the rush command and then trying to create/build an extension would throw some weird errors. This is no longer the case and you'd be just fine aliasing rush command to whatever you want.
The -s (--support-lib) flag used to generate the support library version of your extension even if it didn't depend on any of the AndroidX packages. Now, Rush will warn you when you unnecessary pass -s flag.
There was this little bug that would create a directory named .rush if you run rush build in a non Rush project directory. It is now fixed.
Rush now no longer depend on Apache Ant to build your extensions. All the compilation, optimization, and packaging are now done by Rush itself. 
Tweaked quite a few other things that are either too small to notice or too tough to explain. All you need to know is that Rush is now much more stable and faster than it was before.
To install, as well as to update, follow the new installation instructions:
I hope this update will make extension development a bit more easier and faster. If you face any issues, as always, create an issue here on GitHub or just leave a reply on this topic. I'll try to respond ASAP.
Cheers,
Shreyash
In rush.yml,
how do I enter a multi-line (and/or formatted layout) to description: at the top of the file ?
You can do it like this:
description: |
This is
a multiline
text...Got it... 
Hmmm
Not quite what I meant:
should display as
This is
a multiline
text...
Try to use the <br> tag and try if that works.
Example: This is <br> a multiline <br> text...
Ah, yes. As @Kumaraswamy mentioned, you'll need to add line breaks (<br>) for it to display like that.
Edit: I'm not sure, but maybe you can use \n as well to add a line break. Correct me in case I'm wrong.
OK. This works
description: This is<br>a multi-line<br>text...
but this doesn't ?
description: This is<br>
a multi-line<br>
text...
This just prints out as it is, including the \n
description: This is\na multi-line\ntext...
This doesn't work either...
description: |
This is<br>
a multi-line<br>
text...
If we can use UTF codes someway for special characters, it will be good?
Example:
description: Extension component for TextHighlighter. \u000a By Kumaraswamy Created using Rush.
With this, it won't even let me compile the extension. Although, that's definitely a valid YAML syntax. I guess it's a bug in the YAML parsing library I'm using for the annotation processor... 
Maybe it would be better if Rush detected the multiline YAML strings and automatically added the <br> tags to the compiled extension. Will try to add this feature in a future release.
This isn't valid YAML, BTW.
Rush 1.1.1
You can now see how much time each build took.
...umm, yeah. That's it. This is not a major release after all.
Fixed the inconsistent behavior of property-type blocks. [ref]
Fixed the issue where the extension's assets and the license file won't get compiled within the AIX file.
Fixed the unnecessary invalidation of caches while building the extension. This resulted in slightly increased build times.
Fixed the issue that sometimes caused the Java warning to show more than once.
Fixed some other minor issues.
rush-init). You, as an end-user, won't notice many changes (expect the perky progress bar ), but this will lay the foundation for an upcoming feature that will allow you to upgrade Rush without leaving your terminal.
If you already have Rush installed on your computer, simply download the Rush installer for your OS from the latest release and run it.
If you don't have Rush installed, follow this wiki to install it.
With the previous release (v1.1.1), an issue cropped up that caused the APK creation to fail if the extension used any external library.
So, if you recently upgraded Rush to v1.1.1, I urge you to upgrade it to v1.1.2 ASAP.
If you already have Rush installed on your computer, simply download the Rush installer for your OS from the latest release (v1.1.2), and then run it (it will only update the affected files).
If you don't have Rush installed, follow this wiki to install it.
Greats news ,,
I'm try add an ad extension,
I'm still get error if app build sir @shreyash
Is rush not support other asset like dex file 
Use of DEX files in assets isn't yet supported in Rush. I've got a couple more requests for this feature earlier. I haven't tested anything, but I guess it should be possible to implement it. Although, don't keep your expectations high, I can't promise anything.
