Has the issue been fixed?
Hello, if you are mentioning the dependency problem caused by @ctrl/tinycolor, it is fixed by the latest patch release.
Thank you for sharing more details. I have created a project and tested with the steps that you have provided. However, I could not produce the problem.
I may suggest you to delete node_modules and yarn.lock, and reinstall dependencies since then there would be a problem in the cache. Also, you can remove the @ctrl/tinycolor dependency because the problem is fixed within the latest patch release.
If the problem persists, you can share a sample project via this email sumeyye.kurtulus@volosoft.com.
Hello, this problem has been fixed within the latest patch release that is 9.0.3
Hello again, I have used this command to create a project abp new TestApp -u angular -csf and I could not produce the same problem. Can you please share your steps along with your dependencies in package.json so that I can assist you further?
Hello,
This issue is caused by an update in a third-party package. We're planning to fix it on our side with a patch release soon. In the meantime, you can work around it by adding the dependency manually with this command yarn add @ctrl/tinycolor
Adding extra functions directly to the proxy file is not recommended, as they will be overwritten by the next code generation. Instead, you may create a separate service to handle these additional operations.
If you suspect this issue is related to specific suite configurations or selections, please provide more details so I may assist further.
Thank you for your patience, and I apologize for the delayed response. As you mentioned, the environment variables are configured at the initial stage, as outlined in the ABP documentation: Setting Environment Variables.
That said, it is still possible to override these settings if necessary. The issue you described during the login process might be attributed to a backend misconfiguration, provided that the correct changes are reflected on the frontend.
If the issue persists, I would recommend creating a new ticket and including detailed error logs or specific issues encountered, as the current discussion may no longer accurately address your problem.
Hello,
I have been thoroughly testing this issue using both the CLI and the Studio application across different operating systems. However, I have been unable to reproduce the problem.
For this demonstration, I used the following command to create a new project: abp new TestBreakpointFallacy -u angular -csf, ensuring I was using the latest CLI version as specified in the official documentation. Despite these efforts, the issue does not appear at the specific +/- 1200px breakpoint as described.
Hello, this problem has been resolved with the latest version release referencing this question.
Hello, again. I meant that if you want to see the navigated route highlighted on the navbar, you will need to add them here like this.
