-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Bug] Missing Extensions Options in UnoFeatures starting from Blank Preset when creating projects with Uno Templates, VS Wizard, or Live Wizard #991
Comments
cc @jhanvi03, @Darsh0307 |
Are we missing any additional tests? (cc @nickrandolph for info) From @jeromelaban:
|
Two things from investigation:
|
|
hey there, since this is quite the same I did recognize (but after creation time) I would give some additional detail into consideration: |
Description:
I'm encountering an issue with the latest Uno templates (v5.4.5) and the latest VS Uno Extension (v5.4.11) with Wizard when attempting to add various extensions options to a blank preset project. The issue affects not just Localization, but other extension options such as HTTP as well, which do not get properly reflected in the
<UnoFeatures />
in the .csproj of the project. Below are the details with the Localization option as an example :Steps to Reproduce:
Using Visual Studio Wizard:
Select a Blank Preset project.
Enable Dependency Injection (DI) and Localization.
Create the project.
Observed Behavior: The corresponding entry Localization is missing from
UnoFeatures
in the.csproj
file of the project.MissingLocalizationUnoFeatureWizard.mp4
Using Live Wizard:
Select a Blank Preset project.
Enable Dependency Injection (DI) and Localization.
At the end, notice that option
-loc
is missing from the generated command.Copy and paste the command to manually create the project.
Observed Behavior: Obviously, no corresponding entry Localization in
UnoFeatures
in the.csproj
file of the project.MissingLocalizationUnoFeatureLiveWizard.mp4
Using CLI:
Use the blank preset command (
dotnet new unoapp -preset=blank -o test
) and manually add-di
and the localization option-loc
.Observed Behavior: The corresponding entry Localization is missing from
UnoFeatures
in the.csproj
file of the project.MissingLocalizationUnoFeatureCli.mp4
Additional Observations:
Warning
Adding extensions such as Configuration or HTTP or Localization after selecting DI does not update the command at all, meaning that these options are not included in the generated project.
Live.Wizard.command.Issues.mp4
Expected Behavior:
In all cases, when selecting additional extensions such as Localization, Configuration, or HTTP, these options should be properly reflected in the
UnoFeatures
of the.csproj
file and the generated command (for Live Wizard).The text was updated successfully, but these errors were encountered: