Release notes of LiteFlow 2.6.0, a weapon for decoupling project logic

Preface

Since the release of LiteFlow 2.5.X version dependency, it has successively experienced 10 minor version iterations. The community has also grown steadily, and many friends ask me questions every day.

But I found that the most people ask me: when will the interface layout be supported?

From the perspective of LiteFlow's development plan, interface layout will definitely be supported in the future, but before interface layout is supported. Some foundations must be firmly laid. This is the prerequisite. This is like walking a step. You cannot reach the third step without stepping up to the second step.

So from the planning point of view, the premise foundation is rule dynamic script support .

This time, we brought the 2.6.0-BETA1 version. The version feature is the support of dynamic scripts, and it also supports Ali QLExpress scripts and Groovy scripts. The use documents have all been updated to the official website.

Official homepage: https://yomahub.com/liteflow

Although this is a BETA version, we have worked hard both in terms of underlying rigor and test cases. The official version of 2.6.0 should be released soon.

If you are aware of the LiteFlow framework for the first time, you can go to the following link to learn more:

Gitee warehouse homepage: https://gitee.com/dromara/liteFlow

Github repository homepage: https://github.com/dromara/liteflow

You can also see an article I published earlier introducing the LiteFlow framework

https://mp.weixin.qq.com/s/xyydmtk_a5R1zbg3EeORaw

New version features

Feature #I44FT8 Support script language components, and support dynamic refresh script (version feature)

https://gitee.com/dromara/liteFlow/issues/I44FT8

Feature#I3ZVEA Process component supports retry

https://gitee.com/dromara/liteFlow/issues/I3ZVEA

Enhanced #I40DWO Add business description to the process configuration file, and bring business description into the printing step

https://gitee.com/dromara/liteFlow/issues/I40DWO

Fix #I3VZMZ when the method of recording the execution path of the node in the when type condition scenario will cause data loss

https://gitee.com/dromara/liteFlow/issues/I3VZMZ

Fix #I3UOJG Process termination No data in Slot

https://gitee.com/dromara/liteFlow/issues/I3UOJG

Current project status

The LiteFLow framework is used in core projects by many companies, and there are not many open source process orchestration frameworks in China. LiteFLow's vision is to become the most lightweight and most popular open source framework in the process orchestration field in China.

Currently, there are not many LiteFlow stars, only 500+, and the number of the community is heading toward 300 people. I hope everyone can help us forward and promote it.

We will continue to maintain and iterate on the LiteFlow project. And in terms of ease of use, practicality, performance and official documentation will always be improved and improved.

Follow-up plan

After 2.6.X, start to plan the development plan of 2.7.X, 2.7.X, the interface layout you expect, interface management will be as scheduled. Follow LiteFlow and enter the community group, I will update the development progress in time.

One key triple connection

Still have to say, open source basically uses love to generate electricity, please take three links with one key. Give LiteFlow a star and fork on gitee and github is the biggest support

Gitee warehouse homepage: https://gitee.com/dromara/liteFlow

Github warehouse homepage: https://github.com/dromara/liteflow

recruit

The open source business sounds lofty, but it is not easy to stick to it in practice. Because open source does not make money. Instead, it takes a lot of spare time and energy. But you will also gain a lot.

But many open source authors have persisted in this way, and they are also my role models. China Open Source also needs a lot of love to send more electricity.

If you are also in awe of technology, have a passion for open source, and are optimistic about the LiteFlow project, please join us.

How to join:

1. Join the LiteFLow community group

2. Follow LiteFlow's issue and claim it actively, in the group @我 and inform the claim

3. After completing 2 issues. After reviewing and merging into the master release, give the committer permission

4. Participate in LiteFlow's decision-making, issue contribution, promotion and maintenance in the future

How to join the community

Since the community has more than 200 people, after paying attention, you need to add an author, and then pull you into the community. There are currently nearly 300 people in the community, and there are various leaders who can help you solve the problems in use.