ui-scroll | Unlimited bidirectional scrolling over a limited element | Script Programming library

Okay, so you have bug set A currently baking as 1.5.1-beta2 and you have a new bug set B that you want to get the fix out for immediately. The correct mechanism for this is to fork 1.5.0, fix bug set B, and release 1.5.2 (assuming you don't need a beta). Then merge your B fixes into your A working branch and release 1.5.3-beta1 and proceed to drive that to an official release.

It gets a little more complicated when you have two parallel beta sequences running, particularly when you're not sure which is going to make it to release first, but it is manageable. The key is to to just keep in mind, how SemVer precedence impacts the decisions your customers make (the algorithms they apply), whether to fast-track a particular version into their production systems, verses how their developers pull bits from you.

My production systems, have two inputs:

1. Development is the product of my engineers.
2. Automated maintenance is the product of a system that:
   • Pulls patch releases and applies them to a fork of my current production code.
   • Tests the applied changes against an extensive suite of functional and performance tests.
   • If the tests are green, flight tests the changes in my production environment, while monitoring for unusual changes in production failure rates.
   • As long as everything is going well and a human doesn't step-in to stop it, eventually rolls out the changes to the entire production system.

There are of course, variations for services and packaged products. The point is, you can use your release points to signal to your customers automation, or developers, that you have an important bug fix that has little risk of breaking anything. There is no requirement that 1.5.2 have any lineage back to 1.5.1-beta#. You are not required to ever release a 1.5.1. It is customary however to add a comment in your release notes that 1.5.2 is a hot fix for the bug in 1.5.0 and does not contain the fixes in 1.5.1-beta#.

While you may never encounter a need to do so, you don't have to include the bug fixes from 1.5.2 in your eventual 1.5.3 release, provided the later release, passes your quality controls. It is sometimes the case that a specific bug fix, winds up not being applicable in later releases.

How you maintain your product quality is entirely up to you. How you signal the level of risk/importance for a specific release, is defined by the SemVer standard.

You should not use methods in your template, because each time Angular runs change detection, the method will be called, which can happen often. So actually this is not an infinite loop, the method just gets called on each change detection.

To avoid this, you need to change your code to handle the logic of methods in your component, and use variables in your template instead.

and also as in above comments always use this *ngIf="checkColumnVisibiliy('impressions')" and return boolean instead of this *ngIf="checkColumnVisibiliy('impressions') === true"

Here in your example instead of taking this much variables you can use one model and based on your condition make it true false(default false). That will be easier to use in your code

Try it, please

You can use to precise the width of the columns. Here is an example:

Is it possible to use position sticky on your application?

I've made an example on codepen: https://codepen.io/icaromh/pen/gyJdvZ

If it's possible to use position: sticky it's kinda easy to reproduce it on your code :D

Edit: I've removed a lot of overflows and applied only for the parent div. Also, I've modified some z-index so the headers and first col appear right.

Can I Use: https://caniuse.com/css-sticky

Something is not ok with display css-property in these template and it seems a good idea to extract both viewports into separate div-containers... The following code fixes empty rows issue:

remove width:100% class .zui-scroller

I believe this is a build process responsibility.

Seems you're right. We usually inline template during the build process.

In order to do you can create js file like:

/utils/inline-resouces.js

Get the indexOf the top item and get the indexOf bottom item, and then that should give you all the visible item indexes (between top and bottom).