chore: Convert components to angle bracket syntax

[iamareebjamal]

No description provided.

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/eventyay/open-event-frontend/3ohbww2q4
✅ Preview: https://open-event-frontend-git-fork-iamareebjamal-angle-bracket.eventyay.now.sh

[iamareebjamal]

If you're spending 4x time on solving framework compatibility issues and bugs as compared to fixing bugs and adding features in your own project, there is something seriously wrong in that framework :(((

[iamareebjamal]

Spent 2 hours chasing useless errors and indecipherable stacktraces

[kushthedude]

Spent 2 hours chasing useless errors and indecipherable stacktraces

But alas, Build is still failing 🏗

[iamareebjamal]

It never was successful. This is the thing with ember. I'll try something, it'll fail. I'll curse and vent and come back a week later to be detective again in a crime where I myself am the murderer and the murdered and solve it and break something again and repeat

[iamareebjamal]

So bye for another week and I'll fix it and break something again probably

[snitin315]

Maybe its time to create a new branch and start migrating the project to react bit by bit.
not an easy task 😞

[iamareebjamal]

Let's check by upgrading to octane first and see if it works out. None of it is easy. Neither migrating to react/vue

[iamareebjamal]

I feel like it is some kind of joke where in one place, it is said to upgrade to latest ember and someone else says stay classic
https://twitter.com/mwpastore/status/1246980602412351489

[kushthedude]

Octane is new, but ember has still not dropped support for classic format. Anyway sooner or later, it will drop support and move away from classic forever. So we would need to upgrade anyway, only advantage we can get later is some new and efficient codemods which may not require a lot of labour work perhaps.

…

On Mon, 6 Apr, 2020, 7:42 AM Areeb Jamal, ***@***.***> wrote: I feel like it is some kind of joke where in one place, it is said to upgrade to latest ember and someone else says stay classic https://twitter.com/mwpastore/status/1246980602412351489 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4298 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKQMTLW4SWHTWAQPZYRENHDRLE3AFANCNFSM4MBRZLSA> .

[iamareebjamal]

The weird thing about anyone who is defending ember here is that no one among them is creating PRs to move the project further. I am. And it is exhausting debugging this stuff. So, maybe if @kushthedude can move the project ahead by fixing the PR and handling other required changes to get the project to latest standard. Or should we wait for it to be deprecated?

[kushthedude]

The weird thing about anyone who is defending ember here is that no one among them is creating PRs to move the project further. I am. And it is exhausting debugging this stuff. So, maybe if @kushthedude can move the project ahead by fixing the PR and handling other required changes to get the project to latest standard. Or should we wait for it to be deprecated?

I was just explaining that guy's point of view. Also, I was not the one to choose Ember for the project.

[iamareebjamal]

The migration we are doing here is not octane, it is ES6 classes and angle bracket syntax. And it is not even problem with it, at least ember has codemods. But the debugging is too difficult that it took me an hour to get which component was throwing an error and the error was completely unrelated as well. It originated from ember composable helpers sort by which would not even be needed if ember did not use hbs.

1. Debugging is terribly hard
2. HBS is atrocious to work with and needs 3rd party packages to get basic stuff
3. Packages are not maintained (issue open for 6 months in repo)

[snitin315]

Ember is a nightmare

[jaydgruber]

Hi folks. Please take a look at #4301, which hopefully should provide a template for a more incremental path forward

Also, from personal experience, when I see a team really struggling with and fighting with Ember, and venting some frustration like this, it is because they are cut off from the community.

The majority of Ember developers are not putting their problems and answers up on StackOverflow as you might be used to from other ecosystems. It can be frustrating to google a problem and not find any answers. The best way to find help is to drop into the discord and, I suggest the #topic-octane-migration channel. I think you will find a very welcoming and helpful community there

[iamareebjamal]

Finally! Fingers crossed!!!

[codecov]

Codecov Report

Merging #4298 into development will decrease coverage by 0.06%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development    #4298      +/-   ##
===============================================
- Coverage        22.78%   22.72%   -0.07%     
===============================================
  Files              468      468              
  Lines             4932     4932              
  Branches             5        5              
===============================================
- Hits              1124     1121       -3     
- Misses            3806     3809       +3     
  Partials             2        2              

Impacted Files	Coverage Δ
app/components/tabbed-navigation.js	33.33% <0.00%> (-20.00%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 82070f7...e99ba73. Read the comment docs.