Skip to Content (Press Enter)
Back to Ideas
24
Like
Follow Idea
Forge should block component if it has duplicate SS Key in modules
1483Views
8Comments
On our RadarOn our Radar
Forge

A big problem is when someone downloads a Forge component, makes some changes to it, then re-uploads it to the Forge without using "Clone". The modules end up with the same SS Key as the original component, and then it is total chaos for component consumers because two "separate" components will overwrite each other when they install them (like FileSystem and NetworkFileSystem).

The system should not allow this to happen, Forge should maintain a database of what SS keys are in use by all of the modules in all of the components, and block another component from re-using the SS key.

That will force component makers to either work with the existing component or to properly clone the modules.

J.Ja

26 Sep 2018
Copy link to comment
2020-03-18 17-11-36
Ana de Melo Sequeira
Changed the status to
On our RadarOn our radar

HI Justin


Yes, definitely something that we should solve asap. Let's keep it in our radar to a coming opportunity.


Cheers

Ana

09 Oct 2018
Copy link to comment

Great! Yaaay!

J.Ja

09 Oct 2018
Copy link to comment

It has been a year and a half, please fix this.

I'm sorry, but this is a very easy fix for something that could cause huge issues on any environment. Just check on an existing SS_KEY on forge upload and throw a "denied" message. These "duplicate" components should be avoided. 

We ran into an issue with 2 components that are totally incompatible with eachother but have the same SS_KEY.

https://www.outsystems.com/forge/component-overview/355/advanced-excel

https://www.outsystems.com/forge/component-overview/7469/excel-package-xif

Who knows how many others are out there. The Filesystem mess comes to mind as well.

04 Jun 2020
Copy link to comment

Hi Tim,

This should not be allowed, for sure.

I already contacted the author of the Excel Package XIF to understand why he uploaded it, since this indicates it's just the same module from the Advanced Excel component.


Also deactivated the component to make sure this stops affecting other members. 

04 Jun 2020
Copy link to comment
Merged this idea with 'Forge - List eSpaces/Extensions in a Component' (created on 27 May 2015 16:00:11 by Justin James)
19 Jun 2020
Copy link to comment

Would be nice to see what extensions/eSpaces are in a component before downloading.


J.Ja



This comment was:
- originally posted on idea 'Forge - List eSpaces/Extensions in a Component' (created on 27 May 2015 by Justin James)
- merged to idea 'Forge should block component if it has duplicate SS Key in modules' on 19 Jun 2020 17:08:32 by Sofia Modesto
27 May 2015
Copy link to comment
Changed the status to
New

Hi, thank you for the idea. 

Keep sending ideas :) 



This comment was:
- originally posted on idea 'Forge - List eSpaces/Extensions in a Component' (created on 27 May 2015 by Justin James)
- merged to idea 'Forge should block component if it has duplicate SS Key in modules' on 19 Jun 2020 17:08:32 by Sofia Modesto
19 Jun 2020
Copy link to comment

Such a nice idea which helps in keeping the forge clean and clutter free is "On Radar" for 7 quarters. Please get this implemented. 

20 Jun 2020
Copy link to comment