Fixed: the Roles screen stopped on a role with no rights

If you opened Settings → Roles in the GoCommerce admin and the list of roles never appeared, this was why. It is fixed on main in commit c1ddf61.

What you saw

The Roles screen opened, but the table of roles did not fill in. Nothing was wrong with your roles or your data. The screen hit an error while drawing the list, and stopped there.

When it happened

Every time, as long as the Vendor role had no rights — which is how it ships. Vendor carries nothing until a store grants it something, so a seller cannot see anyone else’s data on their first sign-in.

Why

In Go, an empty list can be “nil”, and nil becomes null in JSON instead of []. The engine sent the Vendor role’s rights as null. The Roles screen asked that list for its length, got an error instead of a number, and stopped.

What changed

The engine now always sends an empty set of rights as []. The change is five lines in core/rights_registry.go. A new test fails if the roles response ever carries "rights":null or "default":null again.

The same null reached one other place. A vendor account’s own sign-in record carried it too, and the panel reads a missing rights list as a static admin token, so it showed that seller the full menu. The engine still refused anything the seller had no right to. With [], the panel now hides those menus as well.

What you need to do

Update to a build of main that includes c1ddf61 (9 October or later), or to the first release after v1.2.0. The fix is in the engine only: no migration, no setting, and no rebuild of the panel. Nothing was saved wrong, so there is nothing to repair.

Further reading

• Custom roles, and adding team members by email — the feature this fix shipped with.
• GoCommerce admin — the panel, screen by screen.
• The fix on GitHub — the diff and its test.