5 Matching Annotations
  1. Jun 2021
    1. In general, top-level errors should only be used for exceptional circumstances when a developer should be made aware that the system had some kind of problem. For example, the GraphQL specification says that when a non-null field returns nil, an error should be added to the "errors" key. This kind of error is not recoverable by the client. Instead, something on the server should be fixed to handle this case. When you want to notify a client some kind of recoverable issue, consider making error messages part of the schema, for example, as in mutation errors.
  2. Feb 2021
    1. When compiling assets with Sprockets, Sprockets needs to decide which top-level targets to compile, usually application.css, application.js, and images.
  3. Oct 2020
    1. (One can already destructure the loop variable but using a store obtained that way currently throws an error - Stores must be declared at the top level of the component (this may change in a future version of Svelte))
  4. Oct 2018
    1. Instead of continuing the millennia old search for the universal ontology, different types of ontologies have been proposed in computer science. [.] [C]lassification of ontologies [is] based on their granularity and [their] thematic scope [differs] into top-level, domain, task, and application ontologies ... (Hitzler, Janowicz, Berg-Cross, Obrst, Sheth, Finin, Cruz 2012)