feat: 🏷️ add deprecated fields to JSON and fetch

[cif]

This is being done as part of Glide tasks:

• #21598 JSON Object: Deprecate "Transform JSON" computation
• #21599 JSON Object: Deprecate "Make JSON Object" computation

Includes a deprecation banner on the REPL beautifully designed by ChatGPT:

Update, this may also deprecate Fetch as well, TBD based on @parkxdavid expert discovery

https://github.com/glideapps/glide/issues/21604

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
glide-code-columns	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 3, 2023 2:22pm

[djpirl]

To clarify, this is the deprecation approach where the developer cannot add new instances?

Is this the general pattern we are taking, or is this specific to these columns?

[cif]

Is this the general pattern we are taking, or is this specific to these columns?

This is yet another set of columns that works differently from the internal plugin system and the older built in options. Still thinking through how to better unify them if at all possible.

Some data around how widely used these columns are in particular would be interesting, happy to try and pair on wether or not that's easy to surface or not

[djpirl]

Is this the general pattern we are taking, or is this specific to these columns?

This is yet another set of columns that works differently from the internal plugin system and the older built in options. Still thinking through how to better unify them if at all possible.

Some data around how widely used these columns are in particular would be interesting, happy to try and pair on wether or not that's easy to surface or not

To clarify my question, what is going to happen to developers who have apps using these columns?

Option A

• Columns still work
• New instances can be added

Option B

• Columns still work
• New instances cannot be added

The banner suggests to me that it's Option B. However, I thought we discussed pursuing Option A. CC @rwdaigle

[rwdaigle]

Correct. We do want Option A to be our definition of deprecated

[djpirl]

Correct. We do want Option A to be our definition of deprecated

In this scenario, what user experience did we merge?

[cif]

No change to builder happens on this merge. This is a rare example of glide code with its own pipeline. Unfortunately, said pipeline needs repair so even this change is not in production (column.sh) yet.

…

On Fri, Oct 6, 2023 at 9:13 PM DJP ***@***.***> wrote: Correct. We do want Option A to be our definition of deprecated <https://www.notion.so/glideapps/Product-Release-Stages-Deprecation-2d100b174d644fdd9d773cfc7f714da0?pvs=4#e08190c1982a46f192b2c9e1542d9ac2> In this scenario, what user experience did we merge? — Reply to this email directly, view it on GitHub <#159 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC7EGNEYSRPH6CJXWXKVMTX6BQ6DAVCNFSM6AAAAAA5Q6IJ7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGM2TGOBXGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[djpirl]

If I'm tracking you correctly, this is upfront work before we ship this banner to users?

[cif]

If I'm tracking you correctly, this is upfront work before we ship this banner to users?

Exactly. The column configurations in this repo get consumed remotely via their metadata residing at this URL: https://column.sh/all.json

[djpirl]

Got it. I can change the copy of this banner as it is not exactly right then

[cif]

That banner only shows up on column.sh website (in this repo).

Seems like the idea here was to open up the ability for open source contributors to create computed columns

[cif]

I just noticed a comment in one of the deprecation issues from @rwdaigle regarding deprecation (not even apps with existing uses will show the column any more).

Would you like me to update the copy to reflect this strategy?