Bug 1590046 Comment 16 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Uday Mewada from comment #15)
> sir, I want to give it one more try.
> As you told I have to introduce `ActionCable` parser in `parsePayload`. 
Correct

> I have seen in the `parsers` directory have different parsers and each parser contains different files.
Correct

> So, which files should I include in Action Cable parser?
> Are the files similar to which are included in SignalR?
Different parsers -> different files

> Only the difference in the properties to be included like https://github.com/rails/rails/blob/master/actioncable/app/javascript/action_cable/connection.js#L123-L138 in the Action Cable parser 
> Or I have to include different files.
These are two different parsers.
SignalR is a library for ASP.NET developers and Action Cable is for Rails developers.

You can look at the comment #1 (there are couple of good links) and understand how the Action Cable protocol works and how to include proper  files for parsing it into Firefox DevTools. Doing these analysis is part of the work on this bug.

Honza
Revision 1 by
on 
(In reply to Uday Mewada from comment #15)
> sir, I want to give it one more try.
> As you told I have to introduce `ActionCable` parser in `parsePayload`. 

Correct

> I have seen in the `parsers` directory have different parsers and each parser contains different files.

Correct

> So, which files should I include in Action Cable parser?
> Are the files similar to which are included in SignalR?

Different parsers -> different files

> Only the difference in the properties to be included like https://github.com/rails/rails/blob/master/actioncable/app/javascript/action_cable/connection.js#L123-L138 in the Action Cable parser 
> Or I have to include different files.

These are two different parsers.
SignalR is a library for ASP.NET developers and Action Cable is for Rails developers.

You can look at the comment #1 (there are couple of good links) and understand how the Action Cable protocol works and how to include proper  files for parsing it into Firefox DevTools. Doing these analysis is part of the work on this bug.

Honza

Back to Bug 1590046 Comment 16