I have a field of type text that has json text… and would like to view it as formatted json, and prevent the users from making changes that corrupts the json format
A field of type json would be perfect for this
Hello @mahmouds12, thanks for sharing your idea. We will discuss it with the team and I’ll share the update with you then 
Hello @mahmouds12, we discussed your idea with the team, and we see the value to add JSON field type. We don’t know when we start working on it, but it’s a great suggestion.
Thanks again for opening this topic 
Please add a JSON field. That would make it much easier to integrate other data sources with BaseRow and will greatly increase the appeal of BaseRow.
Hi @ddsgad, this request is already in our backlog: Support JSON (Objects) as a Field Type (#1240) · Issues · Baserow / baserow · GitLab 
i believe i have this feature (or at least an mvp) done a branch. who do i need to talk to to be able to PR it?
Hey @RejectKid,
We currently don’t accept external contributions unless they’ve been discussed with the team first. You can find more information here: Open source contributions · Issue #5598 · baserow/baserow · GitHub.
Since you already have an MVP ready, I’ll check with the dev team about your request. 
Awesome! yeah happy to go through the proper process with yall. just lemme know how too and naturally go through the back and forth of PR until its in (hopefully)
Hey @RejectKid, first of all, thank you for your contribution. To be honest, we stopped accepting contributions because it was mostly created with AI. This causes tasks to take more time compared to when a developer works on it by themselves.
The difficulty in getting something merged is that it must work at scale, have no bugs, doesn’t break anything else, the architecture of the code is clear, etc. Before we would consider a contribution, I’d love to get a better understanding in how you have created this.
Did you use mostly AI for the JSON field or did you manually ? I’m also curious if you fully understand all the changes and the concepts of introducing a new field type in Baserow. There are a lot of moving parts to consider here.
For sure understandable. And happy to work it to make it how yall need.
Naturally used Ai to help for sure. It’s a large code base 
. But yeah the premise is more so on the UI to be able to hook into the existing jsonb type in postgres. And provide a nice json viewer in the UI. If youve seen nocodb’s implementation of this. Effectively doing the same.
Ideally without breaking anything. But since it’s already in postgres, I feel like it’s a nice natural progression?
Hey @RejectKid, thanks for your response.
Unfortunately, that it does mean that would we can’t accept the contribution The downside is that the initial version with AI is quickly made, also by one of our developers. The work is in the finer details that come after. I don’t mean any offense, but it’s faster for us to develop it internally than working with an open source contributor who used AI to create it. It would also mean that we need to deviate from our current roadmap.
The JSON field is definitely a nice progression. I’m not saying we don’t want to implement it because we do have it on our roadmap.