30 Days with LAST Stack

Hey antisha256,

Yes, those courses are relevant and more specific, i.e. those are standalone courses about Stimulus and Turbo. They are not required to start this course, so feel free to start with LAST and after it start watching Stimulus and then Turbo to learn those technologies better if needed. We cover some basics of them in this course, but if you're planning to work with it more - I would recommend to watch those courses as well.

Cheers!

Hey Mike,

Sure, LAST is our very new course about JS frontend, actually the latest one :) So yes, definitely go with it if you're looking for a modern way of writing websites using Symfony framework with JS integration.

Unfortunately, the LAST stack is too huge to be covered in a tutorial that related to a completely different topic like e.g. Symfony 6 intro course, that's why LAST has its own standalone course. Btw, if you're talking about Symfony 6 in specific - that course was recorded before the LAST course ;)

In short, it's still up to date and our recommendation, but of course it depends on your needs and how you see your website implementation, because some websites may not need JS at all :)

Cheers!

Hi @Erick-E-Alvarez-R

1. It was free for a limited time, and it started to release on 1 December 2023, I even checked all possible dates and can't find any November mentions in the course description, maybe you can get more details about this.
2. Unfortunately, there is no Free filter yet, but I registered it as a feature request in our list and we will process it soon.

Cheers!

Hello @sadikoff, In English, above in the course description, it says the following:

About this course
Symfony 6.4
LAST stack - Live Components, AssetMapper, Stimulus & Turbo - puts the joy, productivity & simplicity back into creating rich, frontend experiences.

However, in Spanish, it says the following:

About this course
Symfony 6.4
Tip

This course is 100% free until January 15th. Enjoy! https://symfonycasts.com/blog/30-days-last-stack-free

LAST stack - Live Components, AssetMapper, Stimulus & Turbo - puts the joy, productivity & simplicity back into creating rich, frontend experiences.

So, above the h1 tag of the title of this page:

https://symfonycasts.com/blog/30-days-last-stack-free

it says Nov 30th, 2023

but as you can see, in the Tip paragraph it says "This course is 100% free until January 15th" but the first impression is that it is until January 15th, 2025.

I want to know about free courses here at SymfonyCasts, I'm very interested in this, and that there is the possibility that you enable free courses for periods of time in the same way that you have done with courses like this one.

Thank you very much, I look forward to your response.

Hi @Erick-E-Alvarez-R

Sorry for the delay in answering your question. Thanks for the patience, we fixed the issue with the description. We'll see if we can publish more courses insuch way =)

Cheers.

Thank you very much @sadikoff.

Regards.

Hey Ruslan,

We do recommend users download the course project code from the video page to follow our courses and 100% match the code that you see in the video. But you can definitely follow it on a newer Symfony version if you want, but you should keep in mind that the code may be slightly different. Actually, Symfony 6.4 that is a base version for this course = Symfony 7 but with a dropped legacy layer, so in theory you should not face any problems. Moreover, we constantly add some important notes to the scripts and video if there's a BD break in a newer version, so you should be extra safe. But if you get stuck following this course on a newer Symfony version - let us know in the comments below and our support team will help you.

Cheers!

Hey Altyn,

We're pleased to hear you like this course! And thank you for your feedback and kind words to Ryan! :)

Cheers!

Hey @JonathanP

Thank you for your kind words. I believe you need a full-page refresh for this case. To make a turbo-frame load the content on the outside you need to add this HTML attribute target="_top"
I recommend watching this video, it shows off how to do fancy stuff after a "modal success" https://symfonycasts.com/screencast/last-stack/modal-success

Cheers!

Hi @MolloKhan , and thank you so much !

I knew it had been explained somewhere (in the turbo-frames video in fact), and I am a little upset at myself for having bothered someone for something that could have been done with a little more commitment to research ...

Again, thank you !

No problem! By the way, at the top of the page we have a search bar where you can look over things related to this course only or through all the courses

Cheers!

Hey OldCoder,

Hm, that's weird behavior, please double-check what exactly you listen to to open the site search modal. Is that internal-input-suggested a pseudo-element? Could you share an example how you use that? Fairly speaking I don't know that internal-input-suggested, but quick googling of it shows that it may cause some issues. I suppose it's only Chrome browser feature? If so, probably that just has a bug with it. Otherwise, try to use it in a different browser, e.g. Firefox. The same behaviour?

I hope that helps!

Cheers!

Hey Tac,

So yeah, login/registeration form is just a regular form so you can handle it in the way we handle forms here. Basically, I bet LiveComponents will do the trick well here. The ApiPlatform might be an overkill for this IMO, but if you're already using that in your project - you can give it a try, though I personally didn't do that before.

About PWA - hm, not sure here, I personally don't have experience in that. So probably a lot of possible edge cases to solve, maybe it's better to watch into more specific tools like VueJS to implement truly SPA, etc.

I hope that helps!

Cheers!

Hey again @escobarcampos!

What a great course as always! I am actually applying the things I've learned here to my current project. Feels good to say good bye to encore!

Woo! Best possible situation!

I am a bit confused on when to use LiveComponents vs TwigComponents. I think I understand the difference... input vs no input? I guess I will need more experience to be able to decide on which to use case by case.

You need a LiveComponent if you need your TwigComponent to reload via Ajax as the user interacts with it. That's a pretty good rule of thumb. But, of course, you can also handle a lot of user interaction just with Stimulus & Turbo. So even if I created a TwigComponent (because maybe I want something to be reusable, or provide its own variables), if I need some interactivity (like submitting a form via Ajax), I might just use Turbo & Stimulus for that. But you can also use LiveComponents, and those are especially useful if the user interaction gets more and more complex.

Btw... do you know of any nice bundle that would make developing simple subscription webapps simpler? (eg. subsription plans, payment methods, orders, returns, recurrent billing, etc.). I found Shapecode but is 4 years old

I don't :/. I hope we can release something some day. I'd recommend checking out Paddle or Lemonsqueezy in general as your payment processor. They can handle a lot of the heavy lifting for you.

Cheers!

Hey @Kilian-K

I'm glad to know you find the tutorial useful. To change when to submit the form, you need to override the getDataModelValue() method from the trait Symfony\UX\LiveComponent\ComponentWithFormTrait

About EasyAdmin, I've not heard that they're planning to integrate LiveComponents but I'd imagine they eventually will. You may want to ask that question in their GitHub repository or perhaps in the Symfony Slack channel

Cheers!

Thank you for the answers MolloKhan, managed to make the validation on debounce happen with your tip! I am guessing the same about EasyAdmin, I guess it will just take a little bit of time!

Have a nice day!

Hey Damien,

It might depend on PhpStorm version. But the Symfony plugin activated and correctly configured (we use a paid version of it in the screencast btw) should do the trick with it. Other plugins - are mostly visual like "Atom Material Icons" and "Rainbow Brackets". Also, Ryan has GitHub's Copilot and Stimulus plugins :)

Cheers!

Hey @Steven!

This is a very good question / thing to notice :). And I think you understand the situation perfectly.

So yes, the real answer is "remove your full build system - you don't need it!". But if there is some tool that you want to use and it's built in Node, absolutely, go for it :). Your setup will still be 95% simpler than it was before. I say a lot about "removing node" because you don't "need" it. And this is such a big change, I'm trying to be clear a about this possibility. The real situation is more nuanced. Start with no-build, Then intelligently opt into tools if you want them. I think many apps may still have no node, but some might, and that's cool :).

Cheers!

Hey Fabrice,

In theory, it should be possible, you should just enable it for those pages in the way we show in our Turbo tutorial: https://symfonycasts.com/screencast/turbo . Though if you watched that course - sometimes Turbo may have some edge cases, that you would need to handle. What I mean is that I haven't done that myself yet, so can't say for sure, but you can easily try it out if you're interested in it and see if it works for you, but be ready to fix some edge cases.

Cheers!

Okay thank you!

Hey @Fabrice!

We'll talk a bit in this tutorial about how Turbo is great, but how you may not be able to enable Turbo Drive immediately in a legacy application. But, Turbo is 2 other pieces (Frames & Drive) and those are much easier to enable even in those situations.

About EasyAdmin, I get this question from time-to-time. I think that EasyAdmin itself will need to update how its JavaScript is organized a bit to allow for Turbo to be used. I would LOVE to see this happen and even help with it. As you'll see in this tutorial, we could do some really nice things like modals, etc easily in EasyAdmin if it embraced Turbo.

Cheers!

Hey! Imagine if we could do this in EasyAdmin, it would be incredible! Looking forward to seeing if this happens, and what possibilities it may offer!

I've opened an issue about it - https://github.com/EasyCorp/EasyAdminBundle/issues/6051 - we'll see :)

Oooh! Nice idea :)

Hey Ruslan,

Thank you for your feedback! What exactly testing are you talking about? The bundles we're using in this course are tested and have tests, you can see it in its repos. Or do you want to see the testing topic covered by this tutorial? Could you give us more context please?

Cheers!

I saw it and it's greate.
I woud like to highlite what 'Testing' is important part in each project, and will be good to see best practice for it.

Thank you.

Hey Ruslan,

I see what you mean. Unfortunately, I'm not sure testing will be covered with this tutorial, that's a completely different topic that requires its own tutorial. There are a lot of testing tools in JS that may help you with it, but mostly you can test it even with Behat/Panther - those tools help you to test UI in a real browser that executes JS, so you literally can open a JS popup, press buttons, send AJAX requests, wait for responses, etc. We have a useful blog post here: https://symfonycasts.com/blog/behat-panther . Also, we have a separate tutorial about Behat testing: https://symfonycasts.com/screencast/behat

I hope that helps!

Cheers!

I WILL spend some time near the end of this tutorial on testing - I have at least 1 day scheduled for it :). I don't know how far we'll get into it (I haven't written this part), but I want to make something real-world & usable.

Cheers!

Testing is why I prefer to separate backend and frontend. It simplifies both backend development (only APIs in Symfony, no Twig, no JS) and frontend development (JS testing in pure-js repository).

I've seen enough legacy Symfony projects with everything combined: Twig, JS, jQuery, Selenium driver, JS-enabled tests. In my experience, for big projects that grow over several years and need maintenance and upgrading, it's better to separate.

Hey @SRP!

I think this is totally fair! However, as a counterpoint, I wouldn't immediately choose the complexity of separating the frontend and backend simply so that my tests are cleaner and faster. Even in that case, I'm going to have end-to-end tests that verify the full user experience.

In the end, choose whichever you're most comfortable & happiest with. This tutorial is about proving that you can choose the Twig path and still build an incredible UI.

Cheers!

Hey @loevgaard ,

Thank you for your interest in SymfonyCasts tutorials! Right now, we're actively working on it :) According to our roadmap: https://symfonycasts.com/courses?status=upcoming&sort=popular#all - it should be the next tutorial that we will start releasing, so it will happen shortly after we finish releasing the "PHPUnit Integration Testing" course.

Cheers!

Thanks :)