Skip to content

Improvement for Weblit web framework. #22

@LeXinshou

Description

@LeXinshou

Hello @creationix, hope you are doing great!

So far, most stable and only open source and running web framework based on Lua/Luvit is the Weblit. However, the development is far behind comparing to other language's web framework. As I am actively working with this framework, I have faced many lacking and many other missing features but the main problem is " Documentation / WIKI " for the framework. I am not very good developer like others but I am doing the things well from my side. Here a few things I have noticed and my request to improve the framework with. ( comparing to Node.JS > Express.JS, Python > Django )

  1. Improvement of the documentation of the framework is must. ( or at least a pre-made package which will install the basic route and other setup. ) [ I am already thinking to create one, soon will release it. ]
  2. Sub domain or sub port or similar administrator panel like Django or Express.JS would be a great idea!
  3. The weblit-static has a issue. When you place domain.name// ( means more than one "/" ) it response with a JSON. Which shouldn't be a thing for production servers.
  4. Having no "/" is also a good thing. We can have the system if you want to create or not create such method. something like
    app.use(requre("redirect")) should remove extensive "/" from the link path.
  5. Sub application would be a great idea!
  6. Weblit doesn't have build in render content system. However, I managed to file one render template in Luvit.io Render file guess, we should have a official HTML render template with syntex {{..}} codeblock system like etLua or others. [ I already have modified one for that]
  7. Having a session manager build in with weblit-cookies would be a great idea. For creating admin panel or user-session or other stuff. [ I have done similar one already here LeXinshou/WebSessionLua but it's not 100% accurate ]
  8. Route system can be improved with more dynamic path listening! ( optional )
    NOTE: I have more in my mind but I don't want to make the whole thing so big to hard to read, during discussion, I will point out more of the stuff that need to be done or improvement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions