Open-event-frontend: Attendee Page: Initializing Tickets showing up in "Completed List"

[mariobehling]

On the attendee page of events initializing tickets are showing up in the "Completed" List

Compare: https://eventyay.com/events/0917096d/tickets/attendees/completed

[sachinchauhan2889]

@mariobehling @iamareebjamal i tried to regenerate this error on eventyay.com and on local host both but error is not regenerated. __Initializing tickets__ are not showing under __completed__ list tab. __Initializing__ tickets are listing under __all__ tab. Could you please tell how to regenerate this error. And __pending__ tab is not available. this is a new issue.

[maze-runnar]

filterOptions = [
        {
          name : 'order',
          op   : 'has',
          val  : {
            name : 'status',
            op   : 'eq',
            val  : 'completed'
          }
        }
      ];

even after applying this the table in completed section showing initialize.
@iamareebjamal this is happening when Ordering more than one tickets at a time, then some of it's tickets go to initialized state, but

 val  : {
            name : 'status',
            op   : 'ne',
            val  : 'initialized'
          }

from here they don't filter, so value coming is correct , but what's showing is not correct.

[maze-runnar]

filterOptions = [
        {
          name : 'order',
          op   : 'has',
          val  : {
            name : 'status',
            op   : 'eq',
            val  : 'completed'
          }
        }
      ];

even after applying this the table in completed section showing initialize.
@iamareebjamal this is happening when Ordering more than one tickets at a time, then some of it's tickets go to initialized state, but

 val  : {
            name : 'status',
            op   : 'ne',
            val  : 'initialized'
          }

from here they don't filter, so value coming is correct , but what's showing is not correct.

@iamareebjamal, what is wrong here?

[maze-runnar]

[maze-runnar]

on clicking on the order link and then going back shows initializing. One solution for this is that open orders/f5c16a44-8692-441f-9bb4-602cc2a41e18/view in new tab. @iamareebjamal ?

[iamareebjamal]

That's not a solution, that's a workaround. Why is it even happening is the question. Is it problem in our our logic, ember-has-many-query, ember-table, ember-data or ember itself

[maze-runnar]

ok, trying to find

[iamareebjamal]

One way of finding is logging the model we are returning. Does it contain initializing orders second time? If so, it is not a problem in ember or ember-table but in ember-data or ember-has-many-query

[maze-runnar]

Does it contain initializing orders second time?

Yes it does in second time -

[iamareebjamal]

It's most likely an error in ember-has-many-query. We need to find out an alternative because it does not work on Ember Data 3.16+ as well

[maze-runnar]

it is also giving a warning, what it means-
You requested a record of type 'order' with id '14645' but the adapter returned a payload with primary data having an id of 'b1459a24-f5eb-43c6-8151-9acb6d928cae'. Use 'store.findRecord()' when the requested id is the same as the one returned by the adapter. In other cases use 'store.queryRecord()' instead.

[iamareebjamal]

Yes, but that warning is of order detail page, not list page

[maze-runnar]

ok

[maze-runnar]

It's most likely an error in ember-has-many-query. We need to find out an alternative because it does not work on Ember Data 3.16+ as well

So what needs to be done for now with this issue? Would it be solve with alternate of ember-has-many-query or opening in new tab for now?

[iamareebjamal]

We need to find out an alternative because it does not work on Ember Data 3.16+ as well

[iamareebjamal]

@maze-runnar Please read https://emberigniter.com/adding-query-parameters-hasmany-relationship/

[maze-runnar]

ok