Starts in:
2 DAYS
1 HR
19 MIN
39 SEC
Starts in:
2 D
1 H
19 M
39 S

Activities of "andmattia"

I try in 5.3.4 same result!

ok I can try with 5.3.4

No I don't have any error and tenant exists

Hi

step to reproduce:

  1. create new empty module (v 5.3.1 with Angular UI and separated IDS)
  2. set multi tenant = true on shared module
  3. start IDS+API+UI
  4. login as admin
  5. create a new tenant
  6. try to login with in the new tenant

You get an error because admin user doesn't exists. So if you look into db the user admin for tenant not exists

ABP 5.3.1 Anuglar

I've create a new module now I need to test in multitenant.

I switch the tenant switch on API side but when I try to create a new tenant doesn't create the admin user

Hi @muhammedaltug

thanks for your quickly reply.

I add some note to integrate your suggestion:

  1. Remove src prefix and * at file name end
//tsconfig.json 
"paths": {
      "your-project": ["projects/your-project/src/public-api.ts"],
      "your-project/proxy": ["projects/your-project/proxy/src/public-api.ts"] // this line added without *
    }
  1. public-api.ts: in projects/your-project/proxy/src/public-api.ts add lib export created before on /proxy/src/lib (not index.ts into /proxy/src/lib/proxy
  2. create a ng-packge.json like this. On github like the suggestion is to create it empty but you must export ts on dist folder
{
  "$schema": "../../../node_modules/ng-packagr/ng-package.schema.json",
  "dest": "../../../dist/your-project/proxy",
  "lib": {
    "entryFile": "src/public-api.ts"
  }
}

  • ABP Framework version: v5.3.1
  • UI type: Angular

We have a module created via suite and now we have crate our nuget pack and NPM to reuse it in another module.

I try to find a way to solve a nightmare related to export module/proxy. All works fine until I need to call a proxy from module B that it came from module A.

I look into a SAAS module and I see that proxy folder is not inside SRC for angular but it was at root level

saas |--proxy |--src

I try to reproduce the same structure but via abp generate-proxy is not possibile... or don't find a way to do that. Looking inside the source I see that ad a ng-package.json to export proxy from module. I do the same but I still get the error module not exported.

My folder structure is ModuleA |--src |-----lib |--------proxy -> In this folder I put ng-package.json

So now I have my build module with proxy epoxrted... but it still no working.

Looking into the generated code I see that SAAS has @volo/abp.ng.saas/proxy into proxy folder but in my module I have @moduleA/src/lib/proxy. I search the documentation where find a way to create a module and NPM package but I don't find anything.

In all module angualr exists only the project foleder and not the entire project (I see that it is refere to a file tsconfig.base.json but where is this file?)

Ok a prepare a full solution and send it

Has you try to build for production?

If you debug it it works fine but is in production mode that customization not work

I send an email with code

Showing 101 to 110 of 142 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06