-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(angular): add Angular Renaissance & update Angular snippets #245
Conversation
9d57e98
to
e4f2c7e
Compare
The build is failing, can you fix it ? As I said it's surely because of a change in |
I can take another look at it tomorrow but I couldn't find what was the issue there |
Well, I took a look at the code of the |
content/3-lifecycle/1-on-mount/angular-renaissance/pagetitle.component.ts
Outdated
Show resolved
Hide resolved
content/4-component-composition/1-props/angular-renaissance/userprofile.component.ts
Outdated
Show resolved
Hide resolved
Can anyone tell what status of this PR is? Are there any issues? |
The status of this PR remains unchanged. I still have the same issues that the ones above and didn't have the time (and probably the knowledge) to fix them.
|
Ok, thanks. Maybe I will have a look if I find time for this. BTW, Angular 19 is making components " |
@LcsGa You introduce a bug and I have to solve it ? That's a little unfair. |
I never told you that you had to solve it yourself. I'm not familiar with the way of doing in the I don't clearly remember how to reproduce it righ now + I changed my computer but I will soon clone it once more, retry, and give more informations if :
The most that I remember at the moment is that I simply tried to build the projects with the provided commands but it failed right away |
Can you give the error logs to begin the investigation ? |
I didn't have the opportunity to retry yet but the error I faced was: pnpm run dev
> [email protected] dev /home/lucas/dev/component-party.dev
> vite
[generateFrameworkContent] Generating framework content files...
TypeError: Cannot read properties of undefined (reading 'push')
at file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2843:40
at async Promise.all (index 4)
at async generateContent (file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2831:7)
at async build (file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2981:7)
at async PluginContext.buildStart (file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2997:9)
at async Promise.all (index 6)
at async PluginContainer.hookParallel (file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:49481:5)
at async PluginContainer.buildStart (file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:49484:5)
at async file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:63425:7
at async httpServer.listen (file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:63440:9)
error when starting dev server:
TypeError: Cannot read properties of undefined (reading 'push')
at file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2843:40
at async Promise.all (index 4)
at async generateContent (file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2831:7)
at async build (file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2981:7)
at async PluginContext.buildStart (file:///home/lucas/dev/component-party.dev/vite.config.js.timestamp-1721509708644-d2f6b8691061.mjs:2997:9)
at async Promise.all (index 6)
at async PluginContainer.hookParallel (file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:49481:5)
at async PluginContainer.buildStart (file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:49484:5)
at async file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:63425:7
at async httpServer.listen (file:///home/lucas/dev/component-party.dev/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:63440:9)
ELIFECYCLE Command failed with exit code 1. |
e4f2c7e
to
b277cc5
Compare
@LcsGa I found the problem. In See "emberOctane" for example |
content/2-templating/5-dom-ref/angularRenaissance/inputfocused.component.ts
Outdated
Show resolved
Hide resolved
content/6-form-input/1-input-text/angularRenaissance/input-hello.component.ts
Outdated
Show resolved
Hide resolved
content/6-form-input/3-radio/angularRenaissance/pick-pill.component.ts
Outdated
Show resolved
Hide resolved
Oh my... I really didn't notice that... The most time consuming bugs are always the most stupid ones I guess... |
I added the modules on purpose! Before angular v14 that was mandatory to create components. Yeah sure! I can do that tomorrow morning I think! 😁 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why have the 3-router-link
and the 4-routing
been removed here? That is not deprecated
They have been removed from other frameworks. |
Oh okay, makes sense! |
I understand but the cost would be too much on other frameworks since there are endless ways to do routing. Yes that's a good point for Angular. |
Ok let's merge it ! Let's iterate if changes are needed ! |
Great! And yes, there will be some new improvements soon (2/3 weeks) 😉 |
Solves the issue #241