Woah are we really that close to seeing it?!
sergio
AstonJ
code-shoily
I have been away from Phoenix for longer than I should have, this HTML aware component is new to me. Will look into this. Phoenix 1.7 looks so good. Thanks for giving me the nudge to get back!
2
tmbb
The p macro could disallow anything that wasn’t a map with constant keys in that case. Personally I rather like the p macro.
0
LostKobrakai
That’ll be confusing at best for beginners, as a map can only be confirmed constant by a macro if it’s provided inline. You cannot do those checks if the map is passed assigned to a variable. This severly limits the usefulness of having a map in the first place (no composition or dynamic aggregation).
You could do the following, but at that point it’s not far from the string interpolation, though a lot more verbose.
map = %{…}
p("/some/:id/path/:another_id", %{id: map.id, another_id: map.another_id})
While I do agree that the path part here is a lot simpler to search/replace, I doubt the same is the case once the dynamic parts of the path change as well.
0
AstonJ
That was a really nice blog post! If you haven’t read it is well worth a read 
From the blog:
In general, the tightly coupled parts of your application should be as close as practically possible. If not the same file, then the same directory, and so on.
I completely agree with that! 
Btw if anyone’s interested here’s another good blog post about 1.7:
Welcome back Mafinar! Programming LiveView book club soon? 
(If anyone else is interested in joining please PM me, I should be able to get you a copy :D)
5
cvkmohan
Hey @Kurisu, Thanks for asking. Yes, I would like to guess again. I do believe we are <2 Weeks into the release of Phoenix 1.7.
Firstly, v1.7 Milestone (github.com) - where all the issues in the milestone are resolved.
Secondly, all the moving parts in the new release mix.exs - live dashboard, liveview and others are moved to semvers rather than pointing to github.
Finally, the commit history is showing mainly typos and trivial documentation changes for the last few days. It means - no major issues pending.
So, my estimate is again 2 weeks. Even a broken clock will be right two times a day - so why not attempt guessing again?
BTW, I am creating new applications using master branch - and - it is working flawlessly so far.
9
darraghenright
Great! I started working on a new LiveView based project for a client a while back, and the project actually had to be postponed for a while. We’re starting again pretty soon so it looks like I’ll be able to use some of these new goodies. LiveView auth is definitely one!
It’s been a while since I watched the keynote that announced a bunch of these features but if I recall correctly Chris McCord hinted a bunch of stuff that would be coming in future releases and I am looking forward to seeing what these will look like in time.
One that I think will be particularly interesting is the proposed fresh look at validating forms — a really easy to use and powerful forms API could be huge.
Anyway, thanks to all the contributors for the upcoming release! Lots of happy devs in this thread 
4
cvkmohan
Now that rc-0 is out -I think 2 weeks for rc-1 and then another 2 weeks for final 1.7 to be out.
Thanks @chrismccord, @josevalim and countless other contributors which made this release happen.
Easily, the most developer friendly web app framework in the world now!
6