Is your feature request related to a problem? Please describe.
Related to #4. Since that's probably not coming back anytime soon, a quick bind function is adequate enough to replace it for the time being.

Describe the solution you'd like
Something like this:

const el = this.bind('div.my-class', EventType.click, this.handleClick);

The devDependency xo was updated from 0.25.3 to 0.25.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

xo is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Another victim of the great moving. Probably just needs to be setup again or is a build issue as nyc and generating cover works fine.

Describe current status
Since the move to remove service dependencies, the current way to get services is a little wordy, especially for ApplicationEventService, which is pretty commonly used.

const appEvents = this.vivi.get('ApplicationEventService');

Describe the outcome you'd like
Shorten names of services and allow for services not to have "Service" after the name. This may require some refactoring in the module factory as get and getFactory is dependent on that.

Additional context
...

Describe the bug
Found while trying to test the following code:

	vivi = new ModuleFactory(
		{
			componentConstructors: [MockComponent],
			rootComponent: MockComponent
		},
		{},
		[{key: 'Logger', override: MockLogger}]
	);
	vivi.get('Logger').setTest(t);

It returns an error on get('Logger') because it's probably registered under 'MockLogger'.

Expected behavior
Overridden services need to registered under the name of the service that they're over ridding.

Additional context
Introduced with #10 feature add

Describe current status
With the recent switch from jest -> ava and slew of refactors, a lot of tests had to be scrapped or rewritten. No more 100% coverage. 😢

Describe the outcome you'd like
With a smallish library like this, 100% isn't impossible. This time around I think some integration tests are in order. Unfortunately with the unit tests we had, they were somewhat fragile because there is so much dependency between classes that any sort of refactoring or clean up caused most of them to break.

Additional context
...

Description
<div class="git" v-if="this.git.errors" v-each="this.git.errors as ErrorsComponent"></div>
This code will throw an error if this.git.errors is undefined.
(Does not throw error if this.git.errors.length is just 0 though)

To Reproduce
Steps to reproduce the behavior:

1. Create a component that has a component that uses v-each on an undefined array

• Running v-if check doesn't work because the v-each runs before v-if.

Expected behavior
Application should crash if v-each is run on an undefined array, either by throwing a warning or ignoring that code if v-if is used.

I also get this error but idk if its the same thing:
Error adding child node: title-section. No root component has been set yet.

Pretty sure I set the root thats set in the module factory constructor.

Originally posted by @griffin8815 in #14 (comment)

The dependency @cspruit/array-like-map was updated from 1.0.1 to 1.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@cspruit/array-like-map is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Describe current status
The new logger is great, but testing with it is somewhat of a nightmare. It doesn't play well with most test runners because it outputs to the console which is...mixed at best. It's fine with AVA as long as the --verbose tag is on, but it does interrupt the output. Honestly Jest was just as bad because it'd show that before the test results. And if you had 1000+ tests like Vivi does...

Additionally - and probably more importantly, if an error is reported, it doesn't fail the test. It'd be nice to configure what fails a test and what is fine. (Like an expected error, for example)

Describe the outcome you'd like
Expand the Logger service for tests that can eat logs if needed and fail/pass tests if certain things happen.

Additional context
Should probably be done before or during #7.

Describe current status
As of writing, Vivi has 4 baked in services, ApplicationEvent, Logger, NodeTree, and ParseEngine.
While NodeTree and ParseEngine are pretty integral to Vivi and would likely not be touched, I can see ApplicationEvent and Logger being annoying for a user that would want a custom solution as ApplicationEvent uses Zephyr for event handling over something like say RxJS and a lot of people like rolling their own logging services.

Describe the outcome you'd like
Allow for custom baked-in services to be injected into the module.

Additional context
This would assist in implementing #8 as it requires Logger to be expanded.

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.7.7 to 7.8.0.

• The devDependency @babel/plugin-proposal-decorators was updated from 7.7.4 to 7.8.0.
• The devDependency @babel/preset-env was updated from 7.8.0 to 7.8.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Move this into the parse engine

https://github.com/CassandraSpruit/Vivi/blob/20a13740db1e69c6ba635085073c17907c38d7e6/src/models/component.class.ts#L70-L75

This issue was generated by todo based on a @todo comment in 20a1374. It's been assigned to @CassandraSpruit because they committed the code.

https://github.com/CassandraSpruit/Vivi/blob/35cff657975cd96ddecf4332771c058119fce1dd/src/services/node-tree.service.ts#L29-L34

This issue was generated by todo based on a @todo comment in 35cff65 when CLeeSpruit/Vivi-Typescript#60 was merged. cc @CassandraSpruit.

Describe the bug
Uncaught TypeError: child.startLoad is not a function

To Reproduce
Steps to reproduce the behavior:

1. Create component
2. In component, create children
3. See error
   Idk if it matters but I also created the factory in the component too

Expected behavior
Should load

Screenshots

Desktop (please complete the following information, if applicable):

• Browser: Chrome

There should be a lot more issues listed in here with the @todo keyword.

It probably got jumbled up during the repo move. Alternatively, jsdocs is somehow messing with it since @todo is also a valid jsdoc tag.

Is your feature request related to a problem? Please describe.
Arrays sorts are pretty common. It would lighten user processing if v-each could handle sorting.

Describe the solution you'd like
Something like this would be nice:
v-each="this.color as ColorComponent; sortBy name ASC"
Or alternatively this might be cleaner:
v-each="this.color as ColorComponent" v-each-sort="name" v-each-sort-dir="asc"

Background
When converting over to TS -> JS, one major feature that was lost was element binding via the ElementDecorator.

This was intentionally dropped because JS does not have a great alternative to TS-esque decorators. They exist if you do tinkering with babel and polyfills, but it would also require the end user to install these.

Additionally, having to create a class variable with a decorator just to bind an element was not a perfect solution to begin with. Often these were manipulated in the class later on in the code, but not always and it'd be flagged by linters.

Workaround
Currently you can just use the old style of grabbing elements and binding events to them. It's a bit wordy though.

Currently Vivi uses Webpack to generate library files for other things to consume it. It's mostly fine except it currently generates only UMD files and there's the webpack.config.js file to maintain.

Look at Zephyr for a good example of implementation.

Describe the bug
When passing data into a child component via v-data-XYZ property, if the value of the attribute is an object, it won't be passed into the child as an object.

To Reproduce
In component
this.info = { puppy: 'bow wow' }

In template
<child-element v-data-info="this.info"></child-element>

Child element will not have an object of { puppy: 'bow wow' }, it'll have a string literal of 'this.info', which is the bug.

Expected behavior
Objects passed into child can be passed via template.

Additional Info
Currently, v-data-* just does a simple replacement like any other attribute. v-data-* will have to be added to the blacklist and custom added to the engine.

To Reproduce
Steps to reproduce the behavior:

1. Create a component through createChild() in the parent component
2. Child component's load() fn will run twice.

This is likely the same bug as #23, just in a different stage in the lifecycle. It's possible the component is created once and then written over again, causing anything in it's lifecycle to run twice, but show more or less correctly in the DOM.

Expected behavior
Load() and other lifecycle functions are only run once per component instance.

Describe the bug
Calling multiple createFactories on the same component will...do just that, but also screws up the component registry.

To Reproduce
Steps to reproduce the behavior:

1. vivi.createFactory(SomeComponent)
2. vivi.createFactory(SomeComponent)
3. Error

Expected behavior
Calling multiple createFactories should just create it once and warn the user if they call it multiple times on the same thing.

https://github.com/CassandraSpruit/Vivi/blob/3f68a2d28cc0c19047d091b6dfc499af1ebbb31a/src/models/component.js#L44-L49

This issue was generated by todo based on a TODO comment in 3f68a2d. It's been assigned to @CassandraSpruit because they committed the code.

Describe the bug
When adding a component with a style attached, it's properly appended to the head, but there's also an extra sibling element that's garbage.

Bug is likely located in the Component.createNodes() section. If I had to guess, the function might be running multiple times and not grabbing the correct existing element.
https://github.com/CassandraSpruit/Vivi/blob/20dd2ace8115d6bedc2995463601f02967c19e2c/src/models/component.js#L85