Why are Progressive Web App Icons circular compared to their App counterparts

Working on a PWA (progressive web app) and coming up with the app icon for it. There aren’t many others around since it’s pretty new but it seems a lot of PWAs use a circular icon to differentiate from the native app.

Is there a particular reason they are choosing a circular icon compared to the many other options? Is this a standard or a guideline(coming from google it wouldn’t be a surprise)?

enter image description here

How to resolve TypeError: Converting circular structure to JSON when creating SP list item?

Trying to create a list item in SharePoint using REST, getting the following error message:

Uncaught TypeError: Converting circular structure to JSON

Am I missing something obvious here?

$  .ajax({         url: _spPageContextInfo.webAbsoluteUrl + "/_api/web/lists('" + myList + "')/items",         type: "POST",         headers: {             "accept": "application/json;odata=verbose",             "content-type": "application/json;odata=verbose",             "X-RequestDigest": $  ("#__REQUESTDIGEST").val()         },         data: JSON.stringify({             'Title': 'testing',             '__metadata': { 'type': 'SP.Data.List_x005f_TasksListItem' }         }),         success: function (data) {             TX = data.d.Id;         },         error: function (error) {             alert(JSON.stringify(error));         }     }); 

WARNING in Circular dependency detected: src\app\app.module.ts -> src\app\app.module.ngfactory.js -> src\app\app.module.ts

Tengo una aplicación con angular, y cuando intento

 ng build --prod 

Siempre sale

WARNING in Circular dependency detected: src\app\app.module.ts -> src\app\app.module.ngfactory.js ->  src\app\app.module.ts 

¿Por que sucede esto, y como puedo solucionarlo?

Muchas gracias por vuestra atención

Circular dependency: Magento\Logging\Model\Handler\Controllers depends on Magento\Logging\Model\Handler\Controllers and vice versa

When i upgrade magento from 2.1.9 to 2.2.0 to 2.2.6 to 2.3.2 i am facing an issue Circular dependency: Magento\Logging\Model\Handler\Controllers depends on Magento\Logging\Model\Handler\Controllers and vice versa. when i execute setup:upgrade command from terminal

TransformedRegion with Circular Sectors

Here is a circular sector:

Disk[{0, 0}, 1, {-\[Pi]/6, \[Pi]/6}] 

I’d like to reflect that about a vertical line. I could use GeometricTransformation with a ReflectionTransform. But I want to access properties of the region, and GeometricTransformation yields False when queried by RegionQ. So, I’m trying TransformedRegion instead.

But there’s some odd behavior. For instance, the following:

TransformedRegion[Disk[{0, 0}, 1, {-\[Pi]/6, \[Pi]/6}],    TransformationFunction[{{-1, 0, 0}, {0, 1, 0}, {0, 0, 1}}]] 

returns Disk[{0, 0}, 1, {-((5 \[Pi])/6), (5 \[Pi])/6}], not what I really want, which is Disk[{0, 0}, 1, {((5 \[Pi])/6), (7 \[Pi])/6}] (a reflection of the original).

That transformation function worked fine using GeometricTransformation. Any thoughts?

How to avoid circular dependency from abstracting navigation in desktop application?

I am trying to abstract some functionality from my desktop application (JavaFX) for changing views.

So, what I am thinking is:

Navigator interface with methods like goToAccountsOverview(), goToAccountDetails(Account account) etc. The implementation will depend on a ViewFactory to create the Views and a DisplayingViewChanger to change the view that is being displayed.

There will be multiple navigator interfaces depending on the state of the application, starting with:

  • NotConnectedStateNavigator (goToConnectToDatabase(), goToCreateDatabase() etc)

  • ConnectedStateNavigator (goToAccountsOverview(), goToAccountDetails(Account account) etc)

So each state will have its own navigator and view factory and a common view changer. The view factories and navigators will not share a common interface (createView(ViewEnum v) and goToView(View view) respectively).

While implementing this I run into a problem. An example of the problem is this:

In the AccountsOverviewView there is a table with all the accounts. Each account has a button to view the details. Pressing that button should navigate to the AccountDetailsView with the ViewModel of the account (I am using some sort of MVVM).

To do that it would call connectedStateNavigator.goToAccountDetails(accountVM) which would call viewChanger.changeView(connectedStateViewFactory.createAccountDetailsView(accountVM)).

So the AccountsOverviewView needs the ConnectedStateNavigator, which needs the ConnectedStateViewFactory, which needs to be able to construct the original AccountsOverviewView, which needs the ConnectedStateNavigator etc.

Some code to explain it better:

public class AccountsOverviewView {     public AccountsOverviewView(ConnectedStateNavigator navigator, ...) {         (...)         accountDetailsButton.onClick(e -> navigator.goToAccountDetails(account));         (...)     } }  public class ConnectedStateNavigator {     public ConnectedStateNavigator(ConnectedStateViewFactory viewFactory, ...) { ... }        public void goToAccountDetails(Account account) {         viewChanger.changeView(viewFactory.createAccountDetailsView(account));     } }  public class ConnectedStateViewFactory {     public ConnectedStateViewFactory(ConnectedStateNavigator navigator, ...) { ... }      public View createAccountsOverviewView() {         return new AccountsOverviewView(new AccountsOverviewViewModel(navigator, ...));     }      public View createAccountDetailsView(Account account) { ... } } 

How could I design this better to avoid this cyclic reference? Is using a setter or an asynchronous event system the only solution?

Custom module causing “Circular dependency” error after upgrading to Magento 2.3.2

I have a custom module with a plugin for Magento\Framework\Encryption\Encryptor that seems to be causing issues after upgrading to Magento 2.3.2 (from 2.3.1.) When I disable the module, everything works fine. When I enable it, I get “No commands in the namespace” for any namespace I try to use. When I run bin/magento list I get a more detailed error message:

In ServiceManager.php line 1130:    An abstract factory could not create an instance of magentosetupconsolecommandbackupcommand(alias: Magento\Setup\Console\Command\BackupCommand).   In ServiceManager.php line 941:    An exception was raised while creating "Magento\Setup\Console\Command\BackupCommand"; no instance returned   In Di.php line 865:    Missing instance/object for parameter maintenanceMode for Magento\Setup\Console\Command\BackupCommand::__construct   In ServiceManager.php line 1130:    An abstract factory could not create an instance of magentoframeworkappmaintenancemode(alias: Magento\Framework\App\MaintenanceMode).   In ServiceManager.php line 941:    An exception was raised while creating "Magento\Framework\App\MaintenanceMode"; no instance returned   In Developer.php line 55:    Circular dependency: Magento\Framework\Logger\Monolog depends on Magento\Framework\Cache\InvalidateLogger and vice versa. 

I’m fairly certain that it’s the plugin on Encryptor causing this, because when I remove that plugin from di.xml the error goes away.

I’ve also tried commenting out all of the methods from the plugin, so that it’s just an empty class, but the error persists. It appears to be the bare fact that there is a plugin registered for that class that is causing the error.

Any ideas why this might be? I’m not sure why enabling a plugin would appear to cause an error somewhere else entirely, especially when that plugin doesn’t even have any methods in it.