@rkever

@rkever

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Issue with multiple checkbox dropdownlist #107258
    rkever
    Participant

    UPDATE:  I just realized most of your stackbliz examples are still using an older version of your package (15.0.2) and I’m assuming because you haven’t updated your module packages (e.g. https://www.npmjs.com/package/@smart-webcomponents-angular/combobox).  I’d suggest you update those and your examples so they don’t get so outdated and make it easier for devs to test out components before they drop them into their projects. I also tested this with a new ang project with latest version, 15.2.10, and that issue is resolved so thanks for that!

    • This reply was modified 8 months ago by rkever.
    in reply to: Issue with multiple checkbox dropdownlist #107256
    rkever
    Participant

    Was this resolved in March release? We’re still seeing the issue in angular (vanilla js web components it’s not an issue).  From your stackbliz we added another component and it quits working. With just one on the page it works fine.  https://stackblitz.com/edit/github-izx8tb?file=src%2Fapp%2Fapp.component.html

    • This reply was modified 8 months ago by rkever.
    in reply to: Distribution problem #103539
    rkever
    Participant

    Awesome sauce Pete and thanks!  I’ll keep an eye out for that on npm too soon.

    in reply to: Distribution problem #103535
    rkever
    Participant

    Appreciate the update. However, still a little concerned as it seems you’re saying there will be no single file that includes all elements in the event you want all available at run time?  I can see that file, the “smart.elements.js” file in the git repo at the source/ root folder. In your npm package, that folder only includes other folders.  So are you eliminating your single file and then require us to manage all components individual files with DI on our own?  I use the single file method for a CMS site that allows any content editors to use any component and I just take the hit during first load. I’m sure I could make my own file but it’s convenient and standard for libs to provide that already.

    • This reply was modified 1 year, 6 months ago by rkever.
    • This reply was modified 1 year, 6 months ago by rkever.
    in reply to: Distribution problem #103531
    rkever
    Participant

    I think there’s still a disconnect here as your demo docs do indeed call out minified js files at the root of source folder as does your main documentation for downloading and installing.  May want to double check this. Not trying to be difficult by any means as I am a big advocate for your framework but my concern here is that when I send folk here, they can easily get confused with incorrect documentation or incorrect npm package structures.

    The below screen shots were scraped from the download and install docs page at https://www.htmlelements.com/docs/download-and-installation/ and your demo page https://www.htmlelements.com/demos/framework/event-binding/ for the framework where it’s a single file that includes all components. Thanks.


     

    • This reply was modified 1 year, 6 months ago by rkever.
    in reply to: Distribution problem #103527
    rkever
    Participant

    I think there still may be some confusion or an error here as there are both “smart.element.js” and “smart.elements.js”  (difference is the “s”) and in all your documents, your examples for loading all components to use “/source/smart.elements.js” and not “source/modules/smart.elements.js” which does not exists in the current npm package.  “smart.elements.js” from what I can tell only exists in the git repo and not the npm package and exists at the root of the source folder and not in the modules.  Can you please confirm if this is an issue?  Thanks.

    git repo screen cap

    • This reply was modified 1 year, 6 months ago by rkever.
Viewing 6 posts - 1 through 6 (of 6 total)