I think you’re suffering from this Known Issue: https://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v12/GUID-069E6E6E-7296-4E79-BF75-E3729BC915C8
See also https://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v12/GUID-E709D04C-36D8-4666-A9D6-A1759C162FF3
Try the following steps to troubleshoot.
Ensure ContentServiceCapability registered with the discovery (DXA model extension works without configuration it's mandatory to register the ContentServiceCapability before content service restart, either install the service with auto-register or run the discovery registration and then restart the service, otherwise ...
Link resolving using proximity logic was indeed implemented in DXA 2.2.
In particular: it was implemented in the DXA 2.2 Model Service and the DXA Model Extension for the GraphQL Content Service.
If you’re using the 9.0 GraphQL Content Service, you have to ensure you deploy the DXA Model Extension which ships with the DXA 2.2 distribution.
If you’re using ...
Sdl.Web.Tridion.Tests contains unit/integration tests for (guess what...) Sdl.Web.Tridion, which is the Tridion provider and model mapping layer in the DXA web app architecture.
There are no unit tests for the Views/Controllers; those are tested by SDL using a suite of system tests, which test the entire web app (incl. modules) through HTTP.
I would suggest best to go for Experience Optimization + some custom build solution.
In SDL Tridion Sites 9.0+ Experience Optimization (XO) - Integrates with very powerfull elasticsearch (replaced Fredhopper) and very extensible and powerfull to manage the rules.
Note that Personalization and Profiling functionality is legacy API (in-process) and is not ...
Yes you can. See the following blog (near the end), or the official documentation.
Sites 9.0 (or rather Content Delivery 11.0.0) is compatible with DXA 1.8, however you won't be able to use the new features introduced, for example content mashups.
URLs like /api/navigation/xyz form the so-called on-demand Navigation API.
This API can only be used when the Dynamic Navigation Provider is configured. This provider uses Taxonomy-based navigation.