When using ABP Suite to add entities / properties, the test cases generated incorrectly tries to add non filterable properties when calling Get methods which will lead to compile errors as those no filterable properties are not parameters of the get method(s).
Hello, I have investigated this problem by the following the same pattern. Your problem should have occurred only for
@abp/ng.feature-managementpackage depending on the optional package selection. Also, thank you for reporting the related deprecations. These issues will be resolved by the next release where you can find details here.
Hi,
Thanks for looking into this. Good to know there will be a general fix coming but will that also fix the deprecated packages warnings? At least they remained for the solution we did as mentioned above. It seems that a fix for that is already in the /dev branch but for whatever reason never made it into 8.3
Please refund ticket as this is now a confirmed bug.
Thanks.
You find the solution in https://abp.io/support/questions/7942/Angular-layered-application-seems-broken-in-83 I believe.
Have you perhaps moved the angular folder from its original kind of awkward position in the folder structure or deselected the "create UI" checkbox? That is the only reason we decided to keep the angular folder in its original location as we assumed this would break if we moved it.
It seems like at least part of these problems are cause by ABP Studio not cleaning up after doing NPM installs. If you uncheck that option in ABP Studio and then do a manual "abp install-libs" you can actually build and run the angular project as well. Still deprecated packages though.
So, looking at the source code for the open source version, it seems like the commercial template is lagging behind here. Looking at the latest app.module.ts there, it is actually updated with what does not seem to work in the commercial template.
In
https://github.com/abpframework/abp/blob/b86c3bee3a7926255c41f7ecc5266f58acdd19e5/templates/app/angular/src/app/app.module.ts
you have for example:
import { provideFeatureManagementConfig } from '@abp/ng.feature-management'; import { provideAbpOAuth } from '@abp/ng.oauth';
But int the ABP Commercial one you still have
import { FeatureManagementModule } from '@abp/ng.feature-management'; import { AbpOAuthModule } from '@abp/ng.oauth';
So the warnings here seems appropriate
Here is the checkin that seems to have updated this in the open source version 4 months ago
https://github.com/abpframework/abp/commit/3c3fb608fd81526c1bc23d391812c3d0787b320a#diff-b8168b298611b9de219c25b8486f54cedf89de46ebdf51c61aa285b97c05c3d5R14
Edit:
Seems to be the entire ABP Commercial Angular version that is lagging behind, including new UI etc.
Extracted from https://abp.io/support/questions/7942/Angular-layered-application-seems-broken-in-83.
It seems like the LeptonX theme breaks for some very certain widths. In our case, it seems to be at 1200 px width in all tested browsers, but make the window only slightly narrower/wider and the problem seem to go away (at least not as obvious). This happens for both Angular and Blazor, but would imagine everywhere as I believe the actual theme is the same.
Moved the LeptonX stuff to https://abp.io/support/questions/7947/ABPLeptonX-theme-breaks-as-specific-widths
Created a new ticket for problems related to LeptonX theme instead to keep this one focused on Angular problems, as they LeptonX bugs seem to be universal.
The packages really seem to be marked with deprecated, even though they were just recently updated
provideFeatureManagementConfig function for config settings.https://www.npmjs.com/package/@abp/ng.feature-management/v/8.3.0
Having looked further into this, it seems like packages.json is missing several dependencies including but not limited to @abp/ng.feature-management.
