Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The dotLess parser traps Exceptions and outputs them to a Logger. The snippet from dotLess's source that performs this is <code>LessEngine.TransformToCss</code>:</p> <pre><code>public string TransformToCss(string source, string fileName) { try { Ruleset ruleset = this.Parser.Parse(source, fileName); Env env = new Env(); env.Compress = this.Compress; Env env2 = env; return ruleset.ToCSS(env2); } catch (ParserException exception) { this.Logger.Error(exception.Message); } return ""; } </code></pre> <p><code>Less.Parse</code> has an overload that takes a <code>DotlessConfiguration</code> object, which provides several properties that you can use:</p> <pre><code>public class DotlessConfiguration { // Properties public bool CacheEnabled { get; set; } public Type LessSource { get; set; } public Type Logger { get; set; } public LogLevel LogLevel { get; set; } public bool MinifyOutput { get; set; } public int Optimization { get; set; } public bool Web { get; set; } } </code></pre> <p>You will notice that the <code>Logger</code> property is of type <code>Type</code>. Whatever type you supply must implement <code>dotless.Core.Loggers.ILogger</code>:</p> <pre><code>public interface ILogger { // Methods void Debug(string message); void Error(string message); void Info(string message); void Log(LogLevel level, string message); void Warn(string message); } </code></pre> <p>As we saw in the first snippet, the <code>Error</code> method on the logger will get called when an error is encountered during parsing.</p> <p>Now, the one sticky point of all this is how exactly an instance of the type that implements <code>ILogger</code> gets instantiated. Internally, dotLess uses an IoC container that is baked into the DLL. Following the method calls, it appears that it will eventually call <code>Activator.CreateInstance</code> to instantiate your ILogger.</p> <p>I hope this is at least somewhat helpful.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I output errors when using .less programmatically?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USquentin-starin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I output errors when using .less programmatically?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COExcellent. Thanks a lot! :-)
      singulars
      1. PO
      1. USAdrian Grigore
    2. COI really should rework the logger API a bit.. At the time of writing it made sense with only the internal usages in mind.. but for external callers this is pretty bad..
      singulars
      1. PO
      1. USTigraine
    3. CO@Tigraine: I hope at least I've explained correctly how to catch logging events, I was a bit unsure if I'd gotten it all down, particularly what the ramifications were of specifying a DotlessConfiguration object with only the logging class filled in. Also, if you are reworking this, I'd point to SimpleLoggingFramework or Common.Logging as two potential facades to logging systems, though honestly it can get to be mess with all the dependencies .... good luck. heh
      singulars
      1. PO
      1. USquentin-starin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload