candango / faz Goto Github PK

Every time we use id in a faz component can will set the console dirty with a warning mentioning that the property could get confuse with the native html id property.

Let's stop to use id and use fazid to identify faz components. For old components supporting id right now let's keep supporting id but we're moving from the this property and using fazid instead.

Stealjs seems abandoned and slow. Let's replace it by webpack.

We need to add a high z-index to the element.

Using data from a json source let's create a main navbar in the show case pages so we only build the navbar once.

This main component may control the selected navbar item.

Instead of processing everything in the nav view model let's move processing to nav items and tab contents.

Let's run karma with electron, webpack and qunit.

When you click on the tab nothing happens.

Let's follow the same line of work from #76.

Lets start to use yarn version 2 style.

They are running under same logic and same code, we just change the instance type and some presentation details.

When we require the nav.less file the request will be fired from the project root instead of from faz root.

Let's use a relative path so we can get the stylesheet directory from the faz project.

Let's create the test infrastructure to faz on travis.

We need to get the exports using the relative path.

Can 6 is out. Let's migrate and use JavaScript classes.

This will be used by any component that needs a list of FazStacheItem to be used to hold children or a collection of items.

Instead of holding a fixed navbar brand and nav lets hold them in a list called items and resolve them in the order they are placed in this list.

A brand can or cannot be a children of a navbar, and we need to add inline forms and the toggler.

Implement https://getbootstrap.com/docs/4.0/components/navs

Let's add the possibility to display categories to the filterbox.

If category is provided we'll show the list with headers showing the category before the list.

If a list has elements with and without categories, the elements without category will be displayed first.

Let's create scripts to clean the previously installed yarn and installation.

The yarn v2 and dependencies will be installed at the end of the execution.

The navbar collapse will hold brand and navs. Before nav was hold brand but that was confusing.

Creating this new level is more intuitive as togglers will trigger collapses actions and internal navs can evolve correctly.

Let's add the target attribute to the nav item in order to add links in another tab or window.

Let's add a form base element so we can control common form tasks.

Instead of mounting rendering the navbar directly from html elements, let's convert them to data format so we can keep the load processing in one place.

Let's update bootstrap from 4 to 5.

Let's make all children a FazStacheItem. Every single component from the FazNavBar will have it's own tag and they will have the responsibility to resolve themselves.

This will clean the code and save some time while we're trying to handle the DOM into loops initialized by the parents.

The pagination buttons' html classes are being resolved in the stache template.

Let's move them to the pagination component.