[ARCHIVED] Did you drop ember.js for Canvas Catalog?

[canvas_support6]

HI,

  We saw most of our JS customisation break with the Catalog change that was pushed on the weekend (3rd Nov 2018). If I inspect the registration-page elements I see that you have dropped the ember.js framework. I don't see this change referenced in any of your release notes anywhere.

   I also found that the 'user defined fields' behaviour has changed. We have a checkbox  label that was propagated to the screen as a text string when in the past it was handled as html.

   Are these intentional changes? if so were they documented anywhere?

   If you are you changing your JS framework? do you have a road map for significant changes like this?

Thanks,
Simon

[jsowalsk]

 @jfenton ‌ can you please provide us some information on this?

[canvas_support6]

Prior to November 3rd our registration pages contained a large number of Ember classes and the Ember elements. These class references have been replaced with generically named classes such as '_3wnIWQ7'. We also saw classes 'registration-summary' and 'inspectlet-sensitive' dropped. Our customer success representative has confirmed that you are 'upgrading' the presentation layer, phasing out Ember and bringing in REACT among other changes.

These changes have generated some re-work for us, firstly to re-write our customisations and secondary to correct our automated test scripts. I would like to know what other changes you have planned before embarking on our rework. Can you provide some guidance on what changes are coming? either a road map, sprint plan or deployment plan.

Thanks,

Simon

[canvas_support6]

Sorry Jessica, I was thinking you were from Canvas when I wrote the above.

[jfenton]

Hey Simon, 

Thanks for reaching out. I'm sorry for the trouble that this has caused. As you know, we've been working mainly on system and backend updates to Catalog. We generally release these without release notes since they do not impact our users directly. However, with our most recent release we also pushed out a change to the registration pages. The fact that this was not communicated out in advance was a definite breakdown in our process. The Catalog team is spending time reviewing and discussing not only how the breakdown happened, but also ensuring that we learn from it and prevent it in the future. Again, I apologize for the additional work that this has created for you and your team. 

As far as future changes the information that you received is correct - we would like to eventually remove all of the Ember from Catalog and replace it with REACT. However, none of that work is currently in progress and we will be certain to communication those changes out well in advance, as well as making the changes available on beta in all regions before they go to prod. 

Please let me know if you have additional questions. 

[canvas_support6]

HI Jon,

   Thanks for the update. We will keep an eye out for the coming REACT changes.

Simon

[jsowalsk]

Today we finally noticed the issue you were speaking of. This is a big issue for us since we have customized our Catalog registration pages and these have been broken due to this update. Can you provide more information  @jfenton ‌ on ways to fix our registration pages back to?