* Updated gitignore to include webstorm
Fixed a bunch of stuff in documentation
Fixed prettier script for windows and then ran prettier since it seemed to not be done
Refactored demos

* Refactored probes

* Added fix script and lint:fix
Renamed a lot of files
Simplified Event Dispatcher
Completely reworked reactions
Reworked probe classes to avoid instantiating so many functions

* Renamed files to include type of file
Reworked event emitters

* Refactoring execution-timeline

* optimized execution timeline to make it much faster

* Fixed performance issues with d3 graphs and fixed some bugs

* Refactored probe manager
Fixed global styles and refactored font families
Refactored timeline more

* wip

* more refactorings and performance improvements. updated packages

* Small change to timeline

* Refactored commands

* Adjusted package.json versions and bootstrap

* misc refactorings regarding commands, plugins, channels, etc.

* Fixed an issue where augury was initializing and dispatching events before the bootstrap code finished. I guess angular 7+ made things start up a lot faster so our code ran after probes were already firing. It's fixed now.

* Fixed memory leak with ScanHistoryReaction

* Added missing test so `yarn test` works

* change detection details component - using on init instead of on changes
renamed elapsed augury event timestamp from auguryHandlingCompletionPerformanceStamp to completedAtTimestamp

* Added augury bridge request type

…40)

We now have 3 major pieces that are very clear and obvious due to these changes: An EventDispatcher that dispatches probes events, a History Manager and a Plugin Manager. Basically works like this:

Plugins ---> Augury/History <---- Event Dispatcher (Probes)

More refactorings are necessary to keep cleaning things up and adding more types, but this is a good step in the right direction I think.

Removed Commands - they are not needed and oddly wired into the event dispatcher just to take part in reactions, but the logic only really depended on the history and nothing else. Removing them eliminated all the coupling with the other major managers/services of augury.

Removed old event dispatcher and renamed ProbeManager to EventDispatcher. These two classes should be combined and were honestly pretty redundant

Removed enhancers. They only applied to 1 event from 1 probe each, and there was no reason the probe itself couldn't just handle it. If we need a way to apply transformations to multiple events coming from different types of probes, we can add it later when we actually have a requirement to do so. I felt like the current design was over-engineered a bit for what we really needed.

Removed reactions. They are no longer needed once commands were removed. Non-command events didn't seem use reactions at all.

Renamed Augury Event types for added consistency. It's actually quite possible that AuguryEventSource isn't even needed anymore.

Drastically simplified references within AuguryCore

Plugins now have a reference to Augury itself, which enables them to interact with the history or create live channels. Now AuguryCore is acting as a Facade to other applications rather than just storing references of other dependencies

Simplified Channels a bit - removed delegate as it wasn't needed.

Renamed all the "EID" fields and made sure all of the plugin/execution timeline interfaces had the same event id and timestamp names to avoid the immense amount of confusion. We really do need add types to all of these Reducers and different types for the AuguryBridgeMessages - it's not very good yet but we can do that in another PR.

Removed NgDebugProbe - it wasn't even doing what the other probes did... it was more like a class filled with helper functions that Commands/Reactions required... and this was not the right place for it. In fact, Enhancers had a reference to the probe manager as a result of this coupling, and it's really good that we removed all of the tangling now.

Changed AuguryEvent interface to a class. We can do more refactoring here over time, but it's much simpler to grok now.

Decoupled bridge reference from the plugin controller/window. Made the bridge into a singleton in case there are multiple plugins active at the same time. It's maybe a good idea to move the bridge into AuguryCore probably.

Removed unused /demos directory. Removed commented out menu options. (#41)

Removed /framework and merged reducers/probes to be in the same folder. We can make finer-tuned adjustments later

Removed Reducers, Scanner, ScannerChannels

Reworked Channels to be simple and assembly

Reworked AuguryBridgeMessage type to accommodate different payload types. Clarified augury bridge message/request types

Added ProbeChannel and AssemblyChannel and reworked Channels in general

Now tracking completion date in Probe class and removed markComplete() - there's no reason to delay this any longer due to the removal of reactions/enhancers - there's nothing to wait for anymore.

Removed ProbeConstructor type and ability to get probes via constructor - it's no longer needed

Added Projection interfaces and EventDragInfo Projection

Rewrote all existing channel and reducer functionality using projections and assemblers. Added types for all outputs on projections/assemblers. Updated plugins and execution timeline angular app to use new augury bridge types and segment types

Performance has improved immeasurably from removing the Scanner.

Refactored all d3 code. Added lots of types and functions and cleanup to separate concerns and make it a bit more readable. D3 is complex if you don't know it, but hopefully this should help a little.

d3 graph now adds new dom nodes when new data comes in without clearing the thousands of existing nodes, thus preventing them from having to be re-added again and again.

The timeline graphs now handle removing nodes too, like when the segments are cleared, without having to manually clear the segments using the old method

Adding ng-add schematics for Augury which will allow user to install Augury through ng add @augury/schematics.

Schematics will do the following:

    Add + Install @augury/core & @augury/performance-profiler-plugin as devDependencies to package.json.
    Add main.augury.ts file
    Add Augury build & serve configuration to angular.json
    Add Augury ng serve script to package.json.

* monorepo + build cleanup

* v0.6.0-beta.0

- Added conventional-changelog & commitlint to maintain consistent commit messages.
- Setup husky git hooks & scripts.
- Fixed some build warnings
- Updated some deps

feat(core) Projection Refactorings

Made all existing projections into assemblers
Renamed all assemblers to projections
Removed all channels
Added augury core project() method to generify projections on the history
Updated all code that this affected
Refactored everything to do Component Trees and Merged component trees
Refactored Life Cycle code counts. Moved all logic into core.
Fixed default brush selection of the timeline

Updated lerna link documentation and updated publishing notes.

* chore: renaming folders

* refactor(examples): updating references to demos

* chore: augury event refactoring

Refactored all augury events into subtypes
Now computing drags when emitting via the Probe and storing as a TimePeriod object
Removed Probe reference from AuguryEvent
Refactored all code to use sub-type events and to no longer use payloads
Refactored ng module code out of probes
Removed tracking of root instance in component hooks probe - we never use it anyway
Created AuguryEvent.isInstanceOf() and changed all code to use this instead of regular instanceof
Changed tsconfig base to use different target and module

Updating the packages to use TypeScript project references support
allows for tooling such as go to definition & refactoring. Also fixed
some build warnings, etc.

refactor: combine connection into single event stream

Refactored bridge to provide an abstraction over the underlying connection. Added a default DirectBridgeConnection which provides. In the future a SocketBridgeConnection may be added to support remote connections from the core/backend and the frontend.

* refactor(frontend): persisting position and size of popup

* refactor(frontend): addressing PR comments on popup

* refactor(frontend): adding header menu to prepare for tabs

* refactor(frontend): moving segment-details to separate row

* refactor(frontend): addressing comments related to template expressions

* chore: fix build watch

* refactor(frontend): make frontend a library instead of angular app

* refactor(frontend): turning frontend into angular elements

* refactor: readding webpack to profiler and cleaning up frontend

* refactor(frontend): adding build:prod script