Bypass collection hook when using LocalAPI

KasparTr

4 weeks ago

5

• 

  thgh

  4 weeks ago

  I would add

  cascade

  in the request and filter that out in the hook so it doesn't make it to the db.

  
  

  Not aware of a way to disable hooks.

  
  

  Eagerly waiting for relational databases 👀

• 

  KasparTr

  4 weeks ago

  What is cascade in request? How can I add that?

• 

  thgh

  4 weeks ago

  I meant a field named cascade with type boolean or text.

  
  

  { name: "cascade", type: "text", hidden: true }

  
  

  When doing the auto-update from the other collection, pass in a value so that the other collection knows not to start a circular loop

  
  

  hooks: {
    beforeChange: [({ data: { cascade, ...data }, req }) => {
      if (cascade !== 'ignore')
        req.payload.update({
          collection: "other",
          data: {
            cascade: "ignore",
            dependentValue: calculate()
           }
        })
      // Same as initial data except "cascade" is missing
      return data
    }],
  }

  
  
  

  It's probably what you described as the not very elegant solution 😛

• 

  KasparTr

  4 weeks ago

  I see, thank that is an interesting hack.

  
  

  The main problem with this approach, is that when you turn cascade off, you also need to make sure it turns back on after the operation has finished.

  
  
  

  Turning cascade on and off are also collection updates so now you have to deal with cascade update triggering the hooks also.

  
  
  

  I implemented this and it somehow works, through additional hacks, but I wouldn't show this code to anyone nor can I sleep at night 😄

• 

  thgh

  3 weeks ago

  The beforeChange hook runs before it hits the database, so cascade is actually never saved.

  
  
  

  By returning a value from the beforeChange hook, it will remove the cascade property from the input.