Base solution for your next web application
Open Closed

Property 'jstree' does not exist on type 'JQuery' #6587


User avatar
0
kasem created

It seems that JQuery was completely removed in your last version. I still need legacy version of JQuery jstree as I made significant updates to organizationTree. But now I get the following error when building the project:

Property 'jstree' does not exist on type 'JQuery<HTMLElement>'.

Another side effect from last update is losing all enums in Angular as they aren't included in service-proxies


7 Answer(s)
  • User Avatar
    0
    kasem created

    JQuery problem is solved by installing the missing package.

    I'm not sure yet about enums generation in proxies and why they aren't supported now

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @kasem

    I'm not sure yet about enums generation in proxies and why they aren't supported now

    Enum generation is also changed, see https://github.com/aspnetzero/aspnet-zero-core/issues/2119

  • User Avatar
    0
    kasem created

    Several discussions on github and I'm not sure I catched the change. Is there any documentation / description about enum change?

  • User Avatar
    0
    ismcagdas created
    Support Team

    @kasem

    No, we have done it on the dev branch. But I think it is not related to your jstree problem. If you want to use it in your project;

  • User Avatar
    0
    kasem created

    Hi @ismcagdas

    I solved jstree problem already.

    I just wanted little details about enum generation in service-proxies as I lost them all. discussion in the link didn't clarify what I should do to get them and where

    P.S. Sorry for mixing two topics in the same ticket

  • User Avatar
    0
    ismcagdas created
    Support Team

    @kasem No problem at all.

    Previously NSWAG was generating enums like below;

    export enum FriendshipState { 
        _1 = 1,
        _2 = 2, 
    }
    

    Because of this dirty definition, we were re-defining enums in some other file with meaningful names. With the issue https://github.com/aspnetzero/aspnet-zero-core/issues/2119 it is changed like below;

    export enum FriendshipState { 
        Accepted = 1,
        Blocked = 2,
    }
    

    So, now we don't have to re-define auto-generated enums anymore.

  • User Avatar
    1
    kasem created

    Perfect! Thank you

    I'll try this and let you know if any questions.