13 Matching Annotations
  1. Nov 2020
    1. BTW, the modules used to be called moduleDirectories in previous versions.
    2. The resolving process is basically simple and distinguishes between three variants: absolute path: require("/home/me/file") relative path: require("../src/file") or require("./file") module path: require("module/lib/file")

      Very important distinction

    3. In contrast to import (which handles 1+2 pretty much the same way, but would send you looking in node_modules right away) path 'module' indeed means your project root for paths without a need to resolve, like output.path in your webpack config... and: (on resolving) Only 3 is subject to resolve.root and resolve.moduleDirectories resolving, see webpack docs here
    4. The problem is that by default, module paths only work with things imported via npm because the new modules variable on resolve defaults to ["node_modules"]. This lets you import 3rd party code from npm really easily. But it means importing your code with a module path needs a config change.
    1. When enabled, symlinked resources are resolved to their real path, not their symlinked location. Note that this may cause module resolution to fail when using tools that symlink packages (like npm link)
    1. resolve: { extensions: ['.jsx', '.js'], modules: [ path.resolve(__dirname, 'src'), 'node_modules' ] },
    2. There was a major refactoring in the resolver (https://github.com/webpack/enhanced-resolve). This means the resolving option were changed too. Mostly simplification and changes that make it more unlikely to configure it incorrectly.
  2. Oct 2020
    1. Returns a Promise<?Object> that resolves with no value on success or resolves with an Object of submission errors on failure. The reason it resolves with errors is to leave rejection for when there is a server or communications error.
  3. Nov 2016
    1. Note: We do not recommend using resolve of AngularUI Router. The recommended approach is to execute any logic needed before beginning the state transition.

      Re: APOD, note that Ionic doesn't recommend the use of resolve. This is the best argument not to!

  4. Dec 2015
    1. Roassal maps objects and connections to graphical elements and edges. In additions, values and metrics are represented in visual dimentions (e.g., width, height, intensity of graphical elements). Such mapping is an expressive way to build flexible and rich visualization. This chapter gives an overview of Roassal and its main API. It covers the essential concepts of Roassal, such as the view, elements, shapes, and interactions.

      I would try a less technical introduction to combine with this one. How about:

      When we're building a visualization, we want the properties of the objects in our domain to be expressed graphically, by shapes, connections and visual dimensions like width, height, intensity of graphical elements. Roassal builds such mappings as an expressive way to build flexible and rich visualizations.

    1. Once a Roassal element has been created, modifying its shape should not result in an update of the element.

      This part should be clarified. Could a further example be referenced?

    2. c := TRCanvas new. shape := TRBoxShape new size: 40. c addShape: shape. shape when: TRMouseClick do: [ :event | event shape remove. c signalUpdate ]. c

      I get this error MessageNotUnderstood: TRMouseLeftClick>>myCircle for this similar code:

      | canvas myCircle data |
      canvas := TRCanvas new.
      myCircle := TREllipseShape new size: 100; color: Color white.
      data := #('lion-o' 'panthro' 'tigro' 'chitara' 'munra' 'ozimandias' 'Dr Manhatan').
      canvas addShape: myCircle.
      myCircle when: TRMouseClick do: [:event | event myCircle remove. canvas signalUpdate  ].

      If I change myCircle with shape it works fine, but I wouldn't imagine that variable names could be so picky. Generic names should work (circle doesn't work neither).