# Ability to "comment out" a component

**URL:** <https://community.glideapps.com/t/ability-to-comment-out-a-component/21803>\
**Category:** Feature Requests\
**Created:** [January 27, 2021, 12:34am UTC](https://community.glideapps.com/t/ability-to-comment-out-a-component/21803 "2021-01-27T00:34:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![forsdick](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/forsdick/32/26296_2.png) [@forsdick](https://community.glideapps.com/u/forsdick)\
**Post date:** [January 27, 2021, 12:34am UTC](https://community.glideapps.com/t/ability-to-comment-out-a-component/21803/1 "2021-01-27T00:34:04Z")

</div>

In the old world of procedural programming, I frequently performed experiments in replacing existing code that already works with some better idea. Rather than delete the part of a program that works with new code that was unproven, I would “comment out” the working code – but not delete it or lose its position. That way, if my new idea and resulting code failed me, I could roll back to the old code that works.

In Glide, the analogous concept would be to have a way to “comment out” components while you tried “something new”. When you get “the something new” to work you could actually delete the old, commented out components.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 27, 2021, 12:42am UTC](https://community.glideapps.com/t/ability-to-comment-out-a-component/21803/2 "2021-01-27T00:42:37Z")

</div>

I usually set a visibility condition with something that will never be true, such as checking if a row id is empty. That’s something that will never happen, so the component is hidden from view.

I do think though that the new editor will have that option to turn visibility on or off.  
Edit: scratch that. I was thinking of something different. Visibility conditions work though to “comment” out a component.

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [January 27, 2021, 12:56am UTC](https://community.glideapps.com/t/ability-to-comment-out-a-component/21803/3 "2021-01-27T00:56:03Z")

</div>

Yep! That’s what I do…I create a component and set the visibility condition to Row Id \> is \> HIDDEN UNTIL…

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 27, 2021, 1:14am UTC](https://community.glideapps.com/t/ability-to-comment-out-a-component/21803/4 "2021-01-27T01:14:22Z")

</div>

Yup, I do exactly what Jeff does.  
I do a similar thing with new tabs. If I’m building a new tab (or replacing an existing one), I just keep it hidden from everyone except myself. Then once it’s ready, I just swap it in.

---

<div class="post-metadata">

**Author:** ![forsdick](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/forsdick/32/26296_2.png) [@forsdick](https://community.glideapps.com/u/forsdick)\
**Post date:** [January 27, 2021, 1:05pm UTC](https://community.glideapps.com/t/ability-to-comment-out-a-component/21803/5 "2021-01-27T13:05:24Z")

</div>

This will work just fine. Thank you.

I do ( as always 🙂 ) have another suggestion. In general it would be nice to show a “hidden” icon in the representation of a component component that is currently hidden ( dynamically hidden due to current list/item state) on in the right column so that you can understand what it going on with a quick look without having to go into the details of a component. Just saying…

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 27, 2021, 1:26pm UTC](https://community.glideapps.com/t/ability-to-comment-out-a-component/21803/6 "2021-01-27T13:26:44Z")

</div>

Yep, that’s what I thought I had seen in the new builder, but it was just for tabs and not for components. Hopefully they will implement your idea.
