Allow seperate updating of demo file for forge components
2350
Views
33
Comments
New
Forge

Hey guys,

I updated the demo of one of my forge components and I wanted to upload this.

However I was required to also reupload my component itself, I even had to increase the version number! Even though the component itself wasn't updated.

I'd love to be able to upload a new demo file without having to update the component itself.

Changed the category to
Community Forge

In the Forge, if we want to add a demo, we have to send the component and demo at the same time.

Please add separate moments where we can submit the component and later the Demo.

Thank you.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:55:33 by Sofia Modesto

I like this idea. This would allow you to update the demo more frequently than you do the component. Especially if more samples or use cases are discovered/required after the component has been completed.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:55:33 by Sofia Modesto

I also ran into this issue. I will only update the demo app when I update the component but the "Try Here" is always to the most up-to-date version demonstration possibilities. You can't however see how the developer did things via this method.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:55:33 by Sofia Modesto
Changed the category to
Community Forge


This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:55:33 by Sofia Modesto

In the Forge, if we want to add a demo, we have to send the component and demo at the same time.

Please add separate moments where we can submit the component and later the Demo.

Thank you.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:09 by Sofia Modesto

I like this idea. This would allow you to update the demo more frequently than you do the component. Especially if more samples or use cases are discovered/required after the component has been completed.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:09 by Sofia Modesto

I also ran into this issue. I will only update the demo app when I update the component but the "Try Here" is always to the most up-to-date version demonstration possibilities. You can't however see how the developer did things via this method.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:09 by Sofia Modesto
Changed the category to
Community Forge


This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:10 by Sofia Modesto

In the Forge, if we want to add a demo, we have to send the component and demo at the same time.

Please add separate moments where we can submit the component and later the Demo.

Thank you.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:11 by Sofia Modesto

I like this idea. This would allow you to update the demo more frequently than you do the component. Especially if more samples or use cases are discovered/required after the component has been completed.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:11 by Sofia Modesto

I also ran into this issue. I will only update the demo app when I update the component but the "Try Here" is always to the most up-to-date version demonstration possibilities. You can't however see how the developer did things via this method.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:11 by Sofia Modesto
Changed the category to
Community Forge


This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:11 by Sofia Modesto

In the Forge, if we want to add a demo, we have to send the component and demo at the same time.

Please add separate moments where we can submit the component and later the Demo.

Thank you.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:12 by Sofia Modesto

I like this idea. This would allow you to update the demo more frequently than you do the component. Especially if more samples or use cases are discovered/required after the component has been completed.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:12 by Sofia Modesto

I also ran into this issue. I will only update the demo app when I update the component but the "Try Here" is always to the most up-to-date version demonstration possibilities. You can't however see how the developer did things via this method.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:12 by Sofia Modesto
Changed the category to
Community Forge


This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:12 by Sofia Modesto

In the Forge, if we want to add a demo, we have to send the component and demo at the same time.

Please add separate moments where we can submit the component and later the Demo.

Thank you.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:13 by Sofia Modesto

I like this idea. This would allow you to update the demo more frequently than you do the component. Especially if more samples or use cases are discovered/required after the component has been completed.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:13 by Sofia Modesto

I also ran into this issue. I will only update the demo app when I update the component but the "Try Here" is always to the most up-to-date version demonstration possibilities. You can't however see how the developer did things via this method.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:13 by Sofia Modesto
Changed the category to
Community Forge


This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:13 by Sofia Modesto
Merged this idea with '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 16:19:18 by Rui Félix)

In the Forge, if we want to add a demo, we have to send the component and demo at the same time.

Please add separate moments where we can submit the component and later the Demo.

Thank you.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:14 by Sofia Modesto

I like this idea. This would allow you to update the demo more frequently than you do the component. Especially if more samples or use cases are discovered/required after the component has been completed.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:14 by Sofia Modesto

I also ran into this issue. I will only update the demo app when I update the component but the "Try Here" is always to the most up-to-date version demonstration possibilities. You can't however see how the developer did things via this method.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:14 by Sofia Modesto
Changed the category to
Community Forge


This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:14 by Sofia Modesto

In the Forge, if we want to add a demo, we have to send the component and demo at the same time.

Please add separate moments where we can submit the component and later the Demo.

Thank you.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:14 by Sofia Modesto

I like this idea. This would allow you to update the demo more frequently than you do the component. Especially if more samples or use cases are discovered/required after the component has been completed.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:14 by Sofia Modesto

I also ran into this issue. I will only update the demo app when I update the component but the "Try Here" is always to the most up-to-date version demonstration possibilities. You can't however see how the developer did things via this method.



This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:15 by Sofia Modesto
Changed the category to
Community Forge


This comment was:
- originally posted on idea '[Forge] Make it possible to add Demo separately from the component' (created on 11 Oct 2019 by Rui Félix)
- merged to idea 'Allow seperate updating of demo file for forge components' on 22 Jun 2020 14:57:15 by Sofia Modesto

Hi Joey, thank you for the idea. 

Can you share more details? Do you have the need to upload the demo more often than the component itself? How often do you upload a new version of a component vs the number of times you need to update a demo only?

Thank you, and keep sending ideas :)
Cheers, 

Sofia.

Hi Sofia,

I myself update the demo more frequently then the component itself. This is because I keep adding methods and implementations examples to the demo. I would like to quickly upload the demo to the Forge for others to see but currently this will also cause an update of the component itself that will trigger an update notification at my consumers with all possible needed QA, even though nothing has changed. 

As for ratios, it depends on the component itself but when I look at my primary component, Leaflet then I would say I would like to update the demo 3 times more then I update the component.

Greetings,

Vincent

I would like to second this. 

Its weird and it unnecessarily forces a new version of the component itself when all I wanted to do was to update the Demo.