rfellows opened a new pull request, #9669:
URL: https://github.com/apache/nifi/pull/9669

   # Summary
   
   [NIFI-14185](https://issues.apache.org/jira/browse/NIFI-14185)
   Migrated to Nx latest (20). This also upgraded to Angular 19. This PR is 
everything required for those changes to be complete.
   
   In angular 19, the default component type is standalone. So if you do not 
declare it `standalone: false`, it will be true. This change had ramifications 
including needing to upgrade some 3rd party components to make them compatible 
as well as relaxing an eslint rule from error to warn when declaring a 
component as `standalone: false`.
   
   There were a couple of new compiler errors that showed up as a result of the 
upgrade too. These were solved in this PR as well.
   
   One particular change to mention, the mat-expand-panel had some behavior 
changes that made scrolling the contents of the documentation panel on load not 
work properly. You will see in this PR that we now initialize state of the 
desired expanded panel based on the current route and control its expanded 
state through properties on the class rather than assume the `openAll` method 
on the accordion will complete in time before the attempt to scroll happens.
   
   # Tracking
   
   Please complete the following tracking steps prior to pull request creation.
   
   ### Issue Tracking
   
   - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue 
created
   
   ### Pull Request Tracking
   
   - [X] Pull Request title starts with Apache NiFi Jira issue number, such as 
`NIFI-00000`
   - [X] Pull Request commit message starts with Apache NiFi Jira issue number, 
as such `NIFI-00000`
   
   ### Pull Request Formatting
   
   - [X] Pull Request based on current revision of the `main` branch
   - [ ] Pull Request refers to a feature branch with one commit containing 
changes
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to