I am trying to implement dhtmlx scheluder with angular which i able to implement successfully with this post, but my concern is i want to so week days at y-axis and time at x-axis. I saw week view inside timeline view and this is what i want to do but unfortunately this one is not working with angular and it's also available in pro version only.
So my question is there any work around to achieve it with out using timeline or pro version ?
Thanks, all answer will be appreciated.
I think you'll have to use the timeline view of dhtmlxScheduler, either that or implementing something from scratch
Since there are no npm packages of PRO versions of dhtmlx components, you have a couple of ways to add the professional version of dhtmlxscheduler to your project:
1) Add scheduler files to your project by hand - just copy scheduler files into a folder in your project and (e.g. src/assets/scheduler) import them from code import './assets/scheduler/codebase/dhtmlxscheduler).
2) If you have a private npm server, you can manually make a npm package from the scheduler codebase - enter the codebase folder of dhtmlxScheduler and run npm init, upload the package to your npm server and install it from there.
Related documentation article: https://docs.dhtmlx.com/scheduler/install_with_bower.html#addingproeditionintoproject
Related
we're working through a setup at my work and I want to see if anyone has any advice/best practices for what we're doing here.
We have code in a git repo for our ui library that produces an npm package (in an internal private registry). That package then gets pulled into the git repos for each of the main products. The question is about versioning the package.
Because we're going from a parallel dev process (git) to linear package versions, which then gets pulled back into another parallel dev process (product git repos), there's an opportunity for code from the library to be accidentally released to production:
Change A is made to the library, produces v1.0
Change B is made to the library, produces v1.1
The library version in a product is updated to v1.1 to access Change B
Product change, and v1.1, is released; Change A in v1.0 is accidentally included
Does anyone have any advice, best practices, or alternate workflows we could keep in mind? The main thing is, we want the UI library stored in one repo but able to be pulled into multiple other repos.
Thank you!
I'm struggling with creating dynamically forms from JSON Schema in Angular 8. I found some libraries for that, but one is very old (last commit ~2 yr ago) and fork of it from this year.
I don't want to use first one, because it's deprecated with angular 8, so my choise was the second one. I have trouble because this project isn't on any npm repositories, only on github. I downloaded it form git like this:
npm i rhalff/angular2-json-schema-form#angular-8
When I started to build my project with this dependency and after attach the import into app.module.ts the result is like this:
ERROR in src/app/app.module.ts:20:65 - error TS2307: Cannot find module 'angular2-json-schema-form'.
I found that in node_module there isn't any src or dist folder and then I looked into github projecet and I found that in /.npmignore there is a src.
I have a some solution about that, but it's not the final one and I think is really bad idea.
I will locally clone git repository, next then build it with npm run build and then npm link
and then npm link <someName> in project catalog.
Can anyone know is there any solution of this problem or maybe someone can suggest me any other libraries for converting JSON Schema for Angular 8 forms?
You may consider using Formly which support json-schema and it provides a bunch of examples to get started https://formly.dev/examples/advanced/json-schema
You can use dynamic-form-schema. It is completely schema based and provide options to add validations, conditional validations and drop down conditional option in the schema.
For more details, check link: Rapid Angular Reactive Form Component Development Based on a Schema
I have one core project(product) in angular. I maintain its repository on github. Every time a new client comes for this product, we create a clone of core project and add customization's according to the client requirements.
Now the problem is, whenever there is some code change in the components of core project we have to manually copy those changes to the clone projects. Lets say we have 100 projects then we have to copy a small code change to 100 projects. Is there any way I can automate this, like every time there is some change in the components of core project, it will get automatically migrated to the clone projects?
I checked the working of npm libraries. It loads all the dependencies in node_modules. I am not sure if I can achieve my objective using this. But please let me know if its possible using npm and how.
The closest solution I can think to what you want to achieve, is to create a shared angular Module or an angular 6 library, from your core project and publish it. For every new client's angular project, Import your core angular library in it and use it. That way you can update your core library anytime and you would only need to run npm update on all the projects that uses the library
And ofcourse you will need to change the architecture of your core project a bit in order to make it a re-usable library. You will need to create generic re-usable components, directives, services, pipes etc and export it.
Also, there are limitations to what changes you can do in the core library that would only require 'npm update' in the other projects to reflect the change
Want to create a react project using create-react-app with the following structure:
project-name dir
-feature1 dir
-feature2 dir
-feature3 dir
package.json
As It can be easily understood from the structure that each feature is going to have it's own directory.
Now the stack holders want the project in such a way that they should be able to run each feature individually in the browser.
i.e.
>cd feature1
feature1> npm start or yarn start
I dont know how to approach this situation. Few months ago I came across a similar project wherein each feature had it's own package.json but that project was broken was not working correctly.
So can anybody guide how can I do this? OR is it even possible to do this? using create-react-app or any other solution?
I'm looking at using Semantic UI in my meteor projects. When I try to run: meteor add semantic:ui I get an error from the terminal saying that the package doesn't exists, yet according the Semantic UI GitHub page it should?
semantic:ui is now Depcrecated , like they point on the nooitaf:semantic-ui package Atmosphere README
try with
meteor add semantic:ui-css
Using Deprecated (not a good choose)
meteor add nooitaf:semantic-ui
We're currently working on relaunching the package. We didnt correctly build the LESS theming into meteor's pipeline in the original package so it did not add any particular value over using semantic:ui-css.
The new package should launch in the next couple days and support theming.
Edit: We just launched the new package, won't be going away again :)
https://atmospherejs.com/semantic/ui