Should we avoid circular dependencies?

Question

When working with Angularjs it is very common to have applications where services contain only HTTP calls to the server that will store the data. However, in an application where we will not have a server our service may be responsible for many business logic (do not worry about the code being visible to the user) and because of this one service may call another and vice versa (this is bad practice).

Imagine the following situation:

angular.module('app').service('logAPI',[ function('fileManager') {

    var _logList = [];

    var LogMessage = function(system, type, message, value, now) {
        this.system = system;
        this.type = type;
        this.message = message;
        this.value = value;
        this.time = now;
    };

    this.scheduleLogMessage = function(system, type, message, value) {
        if (_logList.length < 300) {
            var now = utilAPI.getFormattedTime();
            var log = new LogMessage(system, type, message, value);
            _logList.push(log);
        }
    };

    this.processLog = function() {
        if (_logList.length >= 200) {
            fileManager.upload(_logList[0]);
        }
    };  

}])

.service('fileManager',[ function('storageAPI') {

    var upload = function(obj) {
        storageAPI.upload(obj).then(function success() {
            logAPI.scheduleLogMessage('a', 'a', 'a', 'a');
        }, function error() {
            logAPI.scheduleLogMessage('a', 'a', 'a', 'a');
        })
    }

}])

.controller('appCtrl', ['', function('logAPI'){


    while(true) {
        logAPI.processLog();
    }

}]);

The Angularjs will accuse of circular dependency. Are there ways to circumvent this and the angular 'ignore' this dependency, however, this is bad practice ? We must avoid?

Editing: Improvement of the example

Man logAPI is responsible for managing every log generated by the system and after an X amount of message, it starts uploading those logs. When the upload is done, it can also log in to record what happened. In general, everything in my system generates LOG and because of that, I can’t think of a way to break this dependency.

Answer 1

The best way I know of avoiding circular reference, is to create a separate module, where are the business rules that are common to one or more services. Not just leading to the world of Angular.
On the blog of Misko Hevery, one of the authors of the angular, he quotes exactly that.

Follow the link for consultation: Blog

Editing:

The idea of a logger is that it is like a container of logs and he is responsible for logging in everything. Already his fileManager have to give answers to what he did and not log in.

Therefore, we can use Promises within the fileManager and return a reply to logApi, who is responsible for logging in.

The structure below is more or less a sketch of what we want. (Excuse me the drawing, I had to do in Paint)

And here follows a Jsfiddle with an example for you to base. When you click on the "LOG" button in the example, open the browser console

I hope it helps you