Idea - Separate the process of code rearrangement from publishing

Back to Ideas

Follow Idea

K-Oz

Separate the process of code rearrangement from publishing

On our Radar

1CP

Hello everybody,

When you make a change, for example adding a comment or rearranging statements or actions (without making any changes to your program flow and semantics) then Outsystems always forces you to re-publish your application again.

From a conceptual perspective, making the above changes is a separate process because it does not make any contributions to your programs functionalities.

It would be very nice to see this in Outsystems. I think it will also save a lot of time for the developer (especially in larger projects).

06 Dec 2018

Daniël Kuhlmann

MVP

Hi I agree, only I am pretty sure this idea already is posted in the past.

06 Dec 2018

Tiago Leão

Staff

Changed the category to

1CP

20 Dec 2018

Tiago Leão

Staff

Merged this idea with 'Avoid unnecessary re-compilation' (created on 11 Feb 2019 14:13:33 by Farhad Navaei)

11 Jun 2019

Farhad Navaei

I was wondering if there was a way to avoid any unnecessary re-compilation before deploying new changes. For example, when you resize the flow between two nodes in a workflow, there is no need to recompile the updated module.

By using the Dependency Injection pattern we can read the configuration information from any configured source, such as JSON, XML, or environmental variables. This can be combined by instantiating the services with DI from the configuration information. This way, any changes in the configuration information can be injected dynamically without needing a new compilation.

This comment was:
- originally posted on idea 'Avoid unnecessary re-compilation' (created on 11 Feb 2019 by Farhad Navaei)
- merged to idea 'Separate the process of code rearrangement from publishing' on 11 Jun 2019 18:42:36 by Tiago Leão

11 Feb 2019

Tiago Leão

Staff

Changed the category to

1CP

11 Feb 2019

Tiago Leão

Staff

Changed the status to

On our radar

Hi Kadir,

Thank you for your idea. You are in fact right and there are some improvements that could possibility be done in the publishing process to avoid unnecessary compilations, speeding up the whole process.

We are always looking into speeding up the 1CP process and therefore, I will put idea under our radar in order to evaluate it and check further feedback on it.

11 Jun 2019