[GH-ISSUE #36] Schema definition not enforcing policy on child paths #31

New issue

Closed

opened 2026-05-23 08:26:49 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-23 08:26:49 -06:00

Owner

Originally created by @appy-one on GitHub (Jul 14, 2021).
Original GitHub issue: https://github.com/appy-one/acebase/issues/36

Originally assigned to: @appy-one on GitHub.

When a schema is defined on a certain path, it is not enforcing rules (preventing invalid updates) on target child paths. All works well if data is updated on higher or same paths as the schema definition, but not on deeper paths.

Example:

db.schema.set('clients/*',  { 
   name: 'string',
   contacts: {
      '*': {
         type: 'string',
         name: 'string', 
         email: 'string'
      }
});

let result = db.schema.check('clients/client1', { name: 'Some client', contacts: { contact1: 'invalid contact' } }, false);
// result.ok === false, desired result

result = db.schema.check('clients/client1/contact/contact1', 'invalid contact', false);
// result.ok === true, which is wrong

Fix is on its way

Originally created by @appy-one on GitHub (Jul 14, 2021). Original GitHub issue: https://github.com/appy-one/acebase/issues/36 Originally assigned to: @appy-one on GitHub. When a schema is defined on a certain path, it is not enforcing rules (preventing invalid updates) on target child paths. All works well if data is updated on higher or same paths as the schema definition, but not on deeper paths. Example: ```js db.schema.set('clients/*', { name: 'string', contacts: { '*': { type: 'string', name: 'string', email: 'string' } }); let result = db.schema.check('clients/client1', { name: 'Some client', contacts: { contact1: 'invalid contact' } }, false); // result.ok === false, desired result result = db.schema.check('clients/client1/contact/contact1', 'invalid contact', false); // result.ok === true, which is wrong ``` Fix is on its way