You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am following up here the discussion of #572, I think it is worth having an own dedicated issue for that 😉 @6pac@ghiscoding
It would be worth a consideration to migration SlickGrid to a typescript codebase and try to modernize the codebase by eliminating some dependencies of which some are maybe even unmaintained.
Some benefits on that:
A more modern tech-stack attracts more developers to contribute. Getting new devs bootstrapped and accomodated with the SlickGrid development environment is eaiser this way.
Providing libraries for other projects becomes easier (NPM, TypeScript definitions,..)
Dependency management gets more visible
Removing jQuery makes it more attractive for new frameworks like Angular, React etc. which usually avoid jQuery.
Test infrastructure, documentation etc. is easier to maintain.
Code quality overall can be improved (TSDoc, TypeSafety, OOP development style, module system compatibility,..)
If there is a strategy in this regards, I could try to prepare a basic infrastructure based on my own project which provides bundling, CI/CD scripts, etc. Or you just peek into my structure as a first idea:
It might have a bit more than SlickGrid will need. But especially setting up rollup, typescript, karma, incremental compilation etc. took me a bit, but now it's really smooth (to me at least 😁 ).
@Danielku15 the Discussion tab is now open, can you move your text in a new Discussion.. oh wait there's a button "Convert to discussion", please do that
I am following up here the discussion of #572, I think it is worth having an own dedicated issue for that 😉 @6pac @ghiscoding
It would be worth a consideration to migration SlickGrid to a typescript codebase and try to modernize the codebase by eliminating some dependencies of which some are maybe even unmaintained.
Some benefits on that:
If there is a strategy in this regards, I could try to prepare a basic infrastructure based on my own project which provides bundling, CI/CD scripts, etc. Or you just peek into my structure as a first idea:
It might have a bit more than SlickGrid will need. But especially setting up rollup, typescript, karma, incremental compilation etc. took me a bit, but now it's really smooth (to me at least 😁 ).
The text was updated successfully, but these errors were encountered: