Thank you for your patience! We understand how important this is for your project, and we appreciate your efforts in keeping the discussion going.
The issues you've reported are being considered for upcoming releases, but in the meantime, here are a couple of adjustments that might help:
normalize-css-color dependency, as the error seems specific to web builds.// react-native/src/components/Common/NoRecordSvg.tsx
import React from 'react';
import { View } from 'react-native';
import Svg, { Path, G, Mask } from 'react-native-svg';
function NoRecordSvg() {
return (
<View>
<Svg width={250} height={250} fill="none">
<G id="Group 36278">
<G id="Group 36277">
<Mask
id="mask0_134_2295"
mask-type="luminance"
maskUnits="userSpaceOnUse"
x="0"
y="0"
width="244"
height="244">
<G id="clipPath1535">
<Path id="path1533" d="M0 0H243.339V243.339H0V0Z" fill="white" />
</G>
</Mask>
<G mask="url(#mask0_134_2295)">
<G id="g1531">
<G id="g1537">
<Path
id="path1539"
d="M239.78 109.371H182.633"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1541">
<Path
id="path1543"
d="M133.676 209.136V224.555C133.676 226.99 135.65 228.964 138.085 228.964H167.101"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1545">
<Path
id="path1547"
d="M163.305 228.964H235.368C237.802 228.964 239.777 226.99 239.777 224.555V88.6199C239.777 86.1847 237.802 84.2104 235.368 84.2104H183.295"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1549">
<Path
id="path1551"
d="M58.004 109.371H3.57031"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1553">
<Path
id="path1555"
d="M57.9994 84.2096H45.1719"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1557">
<Path
id="path1559"
d="M46.1142 84.2104H7.9794C5.54459 84.2104 3.57031 86.1847 3.57031 88.6199V224.555C3.57031 226.99 5.54459 228.964 7.9794 228.964H105.268C107.704 228.964 109.678 226.99 109.678 224.555V209.136"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1561">
<Path
id="path1563"
d="M178.714 70.026H59.1602"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1565">
<Path
id="path1567"
d="M157.66 40.9259H64.2593C61.4434 40.9259 59.1602 43.2091 59.1602 46.0256V166.389"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1569">
<Path
id="path1571"
d="M181.878 93.5016V46.0263C181.878 43.2099 179.595 40.9267 176.778 40.9267H157.445"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1573">
<Path
id="path1575"
d="M59.1603 163.313V203.243C59.1603 206.059 61.4435 208.342 64.26 208.342H176.78C179.597 208.342 181.88 206.059 181.88 203.243V92.0845"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1593">
<Path
id="path1595"
d="M77.2734 55.4459H77.3185"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1597">
<Path
id="path1599"
d="M77.2734 55.4469H77.3176"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1601">
<Path
id="path1603"
d="M88.0547 55.4469H88.0988"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
<G id="g1605">
<Path
id="path1607"
d="M98.8438 55.4469H98.8879"
stroke="#1E2025"
strokeWidth="7"
strokeMiterlimit="10"
strokeLinecap="round"
strokeLinejoin="round"
/>
</G>
</G>
</G>
</G>
<G id="Add User">
<Path
id="Fill 1"
opacity="0.8"
d="M144.811 133.157H141.752V130.166C141.752 128.889 140.728 127.848 139.466 127.848C138.206 127.848 137.18 128.889 137.18 130.166V133.157H134.126C132.864 133.157 131.84 134.198 131.84 135.475C131.84 136.752 132.864 137.793 134.126 137.793H137.18V140.787C137.18 142.064 138.206 143.105 139.466 143.105C140.728 143.105 141.752 142.064 141.752 140.787V137.793H144.811C146.07 137.793 147.097 136.752 147.097 135.475C147.097 134.198 146.07 133.157 144.811 133.157Z"
fill="#1E2025"
/>
<Path
id="Fill 4"
d="M115.313 146.959C105.026 146.959 96.2422 148.604 96.2422 155.176C96.2422 161.744 104.972 163.448 115.313 163.448C125.598 163.448 134.384 161.804 134.384 155.232C134.384 148.661 125.654 146.959 115.313 146.959Z"
fill="#1E2025"
/>
<Path
id="Fill 7"
opacity="0.6"
d="M115.318 140.7C122.323 140.7 127.937 135.013 127.937 127.919C127.937 120.824 122.323 115.134 115.318 115.134C108.314 115.134 102.699 120.824 102.699 127.919C102.699 135.013 108.314 140.7 115.318 140.7Z"
fill="#1E2025"
/>
</G>
</G>
</Svg>
</View>
);
}
export default NoRecordSvg;
Since project configurations can impact npx expo-doctor results, providing a minimal reproducible example would allow us to assist more effectively.
Let us know how it goes, and we will do our best to support you!
You're absolutely right to raise this concern. The current setup limits flexibility at some point, and we recognize the need for better control over these options. We will be including the enhancements in the upcoming releases. We appreciate your feedback—it's valuable in shaping a more practical and adaptable LeptonX experience. Thanks for your cooperation!
Hello, thank you for bringing this up!
This behavior is intentional, but if you would like the login button to appear in the mobile navbar, you can use component replacement with eThemeLeptonXComponents.MobileNavbarProfile as a workaround. You can find documentation here: https://abp.io/docs/latest/framework/ui/angular/component-replacement
We’re also open to revisiting the menu structure in future updates. Let me know if you need any help implementing this!
The issue is resolved within the latest release. Can you confirm that your problem is also solved?
Thank you for providing extra details. This problem is solved and related release will be available today. I can suggest you to upgrade to 9.1 until then. I am also refunding your ticket.
Hello, could you please share your package.json if your problem persists?
No, there will be no new item added since I suggested a patch for the parent route. If you can provide how you have implemented the solution, I can assist you further.
Hello, the new route will not be recognized by the navigation configuration if you did not add it to the routes. Because of this, the navigation bar item is not highlighted.
I can suggest you to patch the navigation item according to the navigated details page manually for the time being as explained here: https://abp.io/docs/latest/framework/ui/angular/modifying-the-menu#how-to-patch-or-remove-a-navigation-element
This will require further configuration based on your requirements, but here is a small workaround example:
import { RoutesService } from '@abp/ng.core';
import { Component, inject } from '@angular/core';
@Component({
selector: 'app-root',
template: `
...
`,
})
export class AppComponent {
private routesService = inject(RoutesService);
constructor() {
this.routesService.patch('::Menu:Dashboard', {
path: '/dashboard/test',
});
}
}
import { NgModule } from '@angular/core';
import { RouterModule, Routes } from '@angular/router';
import { DashboardComponent } from './dashboard.component';
import { DashboardTestComponent } from '../dashboard-test/dashboard-test.component';
const routes: Routes = [
{
path: '',
component: DashboardComponent,
children: [{ path: 'test', component: DashboardTestComponent }],
},
];
@NgModule({
imports: [RouterModule.forChild(routes)],
exports: [RouterModule],
})
export class DashboardRoutingModule {}
You're very welcome! I'm happy to assist and look forward to hearing how it goes. Please don't hesitate to reach out if you need any further support.
Yes, exactly. It depends on how you want to implement the override. You can use the component replacement along with the NavbarComponent which may be shorter and easier.
You can also give a path reference in your tsconfig.json as in the screenshot.
