New: per-page position.json files for protected multipage apps

📣 Retool Announcements
1

Hi everyone!

With multipage apps enabling more people to work on the same app, we're working on ways to reduce merge conflicts in source control. One major pain point was the .positions.json file, which often caused conflicts when multiple people moved components around.

To address this, we’ve introduced per-page .positions.json files instead of a single global file—it should significantly reduce conflicts when working on different pages simultaneously.

Here’s an example of how your Toolscript files could be structured with per-page position files:

app-name
└── .defaults.json
└── .positions
  └── .global_mobile_positions.json
  └── .global_positions.json
  └── .pageName1.positions.json
  └── .pageName2.positions.json
  └── .pageName1.mobilePositions.json
  └── .pageName2.mobilePositions.json
└── lib
  └── sqlQueryName.sql
  └── jsQueryName.js
└── src
  └── container1.rsx
└── functions.rsx
└── main.rsx
└── metadata.json

If you'd like this feature enabled for your organization, drop your org email below!

9 Likes
2

Hi @Isabella_Borkovic,

I’m excited about the new per-page .positions.json feature! It will definitely help reduce merge conflicts when working on multipage apps. I’d love to have this feature enabled for my organization. Here’s my email address: info@widle.studio

4 Likes
3

This is great! Does this mean existing multipage applications will auto-generate per-page position.json files on editor open?

4

Yes!

5

Enabled! Let me know if you don't see the changes on your end!