By default the Android project has Dex compiler and Code Shrinker set to blank. Dex compiler needs to be set to D8 and Code Shrinker needs to be set to R8.

What would you like to be added:

Changes to tube-player page

Why is this needed:

Incomplete + a couple broken links

Anything else we need to know?

Discussed internally with @agneszitte

I finished to the end of Module 05 and it wasn't clear that the app was finished (I thought solution files were missing for subsequent modules). It might make sense to explicitly state that the app is complete at the beginning of the readme for subsequent modules.

Current behavior

When I'm on this doc and click on Improve this Doc link it goes to the wrong place.

Expected behavior

The Improve this Doc leads me to the correct place.

How to reproduce it (as minimally and precisely as possible)

Anything else we need to know?

CI for TodoApp

The goal is to avoid having non-working solutions for the workshop.

Requirements:

• It must use Azure Pipelines with a azure-pipelines.yml file.
• All solutions must build correctly (no need for artifacts)
• Optional: the resulting applications should be tested to work properly using UI Tests

A good example would be the one defined with Uado: https://github.com/unoplatform/uado/blob/master/azure-pipelines.yml

Current behavior

Here it says:

Note usage of partial classes and the naming the convention of MyControl.cs, MyControl.iOS.cs, MyControl.Droid.cs, MyControl.wasm.cs.

Expected behavior

But the actual naming convention for Android is MyControl.Android.cs

I found moving from Module 4 to Module 5 the source code for app for Module 5 was missing the code from Module 4. The source code should always included the completed code from the previous module. This avoids build errors and confusion for new students.

Within module 4 there is a step to update the view bounds for iOS. The problem is Windows VS2019 would not be able to do this step. It would be better to have Android UI example here instead.

Here should be row 1 instead of 2. Currently it shows the output behind the keypad.

Module 4 is missing steps to complete the MainPage UI around the Radio button controls.

What would you like to be added:

Solution filters that attendees use to load only UWP and WASM.

Why is this needed:

Allows workshop to focus on WASM/UWP without having an attached mac or android emulators installed.

Anything else we need to know?

Alternatively make it so these projects are not build by default.

Dependabot couldn't find a .(cs|vb|fs)proj for this project.

Dependabot requires a .(cs|vb|fs)proj to evaluate your project's current .NET dependencies. It had expected to find one at the path: /<anything>.(cs|vb|fs)proj.

If this isn't a .NET project, or if it is a library, you may wish to disable updates for it in the .dependabot/config.yml file in this repo.

You can mention @dependabot in the comments below to contact the Dependabot team.

Trying to refactor/move large chunks of code around leads to a lot of confusion for people when trying to deal with all the trailing brackets and semicolons that need to be moved around.

We need to think of a better way to walk people through:

1. Refactoring the ListView ItemTemplate into the VideoItemTemplate method
2. Moving the ListView into the FeedView ValueTemplate
3. Adding the other FeedView templates

Trying to get people to copy just the right section of code from the generated pages for NoneTemplate/ErrorTemplate in the plugin is very difficult

What would you like to be added:

ApiInformation.Is[Method|Event|UnoThing]Present exists and can be used to test/check for API's which haven't yet been implemented.

https://github.com/unoplatform/uno/blob/master/src/Uno.Foundation/Metadata/ApiInformation.cs#L36

Why is this needed:

Increase awareness of the tool and share best practices show it should be used.

Anything else we need to know?

Clicking on source code leads to a broken page

https://platform.uno/docs/articles/external/workshops/simple-calc/modules/MVUX-XAML/01-Build%20your%20first%20Project/README.html?tabs=wizard#prepare-the-project

I've never used Figma before, so I'm not aware if this is due to a recent UI change or what, but I'm currently unable to import the UI from Figma. I can duplicate and open the Figma project, and I can install the extension, but there's no "Export Tab" that has an option for XAML. The only options are exporting from File -> Export - which doesn't work, as it states none of the selected layers have "export settings" - and exporting at the bottom of the inspect module, which only allows for exporting as an image.

If this is something that's just due to me not being with familiar with Figma, then I think it would be a good idea to put a little tutorial about Figma in the guide, as well. I practically turned the entire website upside-down trying to look for the Export tab in the tutorial.

What would you like to be added:

Correct the grammatical errors in the LICENSE file

Why is this needed:

 For smoothness of Reading

Anything else we need to know?

 NO

What would you like to be added:

unoplatform/uno#1564

Why is this needed:

https://twitter.com/GeoffreyHuntley/status/1175098875926994945

Anything else we need to know?

What would you like to be added:

In the 99 Ship your app module WASM debugging is not enabled by default. This should be changed.

Right now, when using docs, the Get Started section is under the Simple Calc tutorials, which seems to be wrong. See screenshot below.

I presume the correct behavior would be for the Getting Started section be a top-level section, since it's a general topic. I don't know how to fix this one, so I'm opening this issue here.

reference: https://platform.uno/docs/articles/external/workshops/simple-calc/modules/Getting%20Started/README.html

This step includes instructions on replacing the loosely-typed bindings generated by Figma with strongly-typed ones by using a Find and Replace with regex that is pretty hard for people to follow.

Is it absolutely necessary to use strongly-typed bindings?

Why is this needed:

Feedback from attendee that workshop it's not clear if one should incrementally build the application or close and move onto the next (which incorporates the previous work)

Anything else we need to know?