Aaron1178

{
   SNew(SListView<ItemType>)
  .ListItemsSource(ItemSource)
  .SelectionMode(ESelectionMode::Single)
  .OnGenerateRow(this->OnGenerateRow)
  .HeaderRow
  (
  this->HeaderRow
  )
}

Aaron1178

FAssetRegistryModule& AssetRegistryModule = FModuleManager::LoadModuleChecked<FAssetRegistryModule>(FName("AssetRegistry"));
IAssetRegistry& AssetRegistry = AssetRegistryModule.Get();

TArray<FString> ContentPaths;
ContentPaths.Add("/Game");
AssetRegistry.ScanPathsSynchronous(ContentPaths, true);

// Use the asset registry to get the set of all class names deriving from Base
TSet< FName > DerivedNames;
{

Aaron1178

void UMyAssetManager::StartInitialLoading()
{
	Super::StartInitialLoading();

	UE_LOG(LogMyAssetManager, Log, TEXT("Initializing MyAssetManager"))

	if ( !bHasScannedForWidgetBlueprints )
	{
    	    /** Scan for and Register Widget Blueprints with the Asset Manager*/
   	    Get().RegisterWidgetBlueprintsPrimaryAssets<UMyBaseUUserWidgetClass>();

Aaron1178

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.