Detail Grid with stick columns

[Noah]

I see that sticky columns in master/detail grids aren't supported. But if the sticky column is on the right of the grid, it seems to work fine.  Is there a potential risk I'm overlooking?  We have grids with potentially long rows, but want to keep the command button on the far right showing regardless of how wide the rows are.

If you don't see it causing subtle issues I'm not noticing now, is there any way to suppress the exceptions it throws in development mode?

[Georgi]

Hello Noah, 

Thank you very much for the details provided.

If I understood you correctly, you are currently utilizing the Kendo UI for Angular Master-Detail Grid and are experiencing some unexpected behavior with the built-in sticky option of the component's columns. Please, correct me if I misunderstood you. 

Indeed, you are correct that utilizing the built-in DetailTemplateDirective together with the sticky columns is not supported as suggested in the Known Limitations section of the Sticky Columns article: 

With that being said, I used the provided details to try to reproduce the behavior where the Master-Detail Grid and the sticky columns manage to work simultaneously. However, it seems to me that I might be missing out on some of the reproduction steps since an error is being thrown on my side once the sticky property of any of the columns is set to true. For reference, I am sending you a StackBlitz demo that demonstrates this behavior as well as a small Angular application: 

https://stackblitz.com/edit/angular-ex6nzx

To run the attached application: 

1. Unzip the folder.
2. Run npm install.
3. Run ng serve.

In these lines of words, I would like to mention that if there is another Grid in the details section of the Master-Detail Grid, the developer could set any of the columns in the detail Grid to sticky and no corresponding errors will be thrown:

https://stackblitz.com/edit/angular-s38tnp

When it comes to removing the error messages on the console, what I would suggest would be for the developer to obtain the source code of our components, identify the row in the verifySettings() method of the grid.component.ts file, and remove the row that is responsible for throwing the error message. Furthermore, it is also important to mention that these errors are only visible in development mode and won't be displayed in production.

I hope the provided information sheds some light on the matter. Please, let me know if I am missing out on something.

Regards,
Georgi
Progress Telerik