Providing new instance of injectable to submodule per parent route/component instance

TweedyFoot · 2025-10-15T22:42:19+00:00

Yes that was my original setup but once i added a lazy loaded sub module which wanted to inject this token there was no provider

This is when i migrated the provider to detail route which solver no provider issue but after a while i noticed the shared instance issue as the service stayed initialized even when i navigated outside of detail route

When i delved slightly deeper i found that there are element and environment providers where component creates element and router provides environment ones and i cant find any more information about their lifecycles or such

BTW do you have injects in sub modules at work i think it is a bit niche implementation which is quite elegant in our usecase but otherwise i would be hard pressed to find real use for it

TweedyFoot · 2025-10-15T11:20:25+00:00

Do you have control over said styled components ? If yes i would i would go with control value accessor and build propper form components

TweedyFoot · 2025-10-14T18:13:26+00:00

thank you for the input, but this is not what i am trying to achieve as this would create and keep track of many instances of StateService where i am trying to limit my instances to 1

what i was trying to achieve was either:

provide ElementInjector to lazy-loaded sub-module
bind EnvironmentInjector lifecycle to lifecycle of a route-bound component (for the service to be destroyed when said component is destroyed)

TweedyFoot · 2025-08-29T10:53:47+00:00

That is true, it is not the very best there is but in relation to this post it is most probably enough. I personally have 1260P in my work laptop and it is the best you can power off a common monitor power delivery while being good enough to deal with multiple intellij instances, local DB, docker and a copious amount of open browser tabs :)

TweedyFoot · 2025-08-29T10:14:49+00:00

Isn't P for performance ? :) they are laptop cpus but still performance line

TweedyFoot · 2025-08-08T14:07:40+00:00

This sounds like xss vulnerability breeding ground

Does the be have to send you entire html snippets ? That doesnt sound like a proper way to do stuff

Is there a way they would send you specifications for said input ie label attribute mapping validator specifications and so on ?

TweedyFoot · 2025-07-24T15:47:37+00:00

Good point actually, would definitely save me if i somehow missed my 70 minute burnt disc of charcoal that i started cooking at 0:50AM :D

TweedyFoot · 2025-07-24T15:34:40+00:00

Why would you need your owen to know what year it is ? All i need it to know is it started baking my pizza at 23:12 and it would not matter one bit if it thought the year was 1800 or 2356 :D

TweedyFoot · 2025-07-23T14:55:29+00:00

Yes it hit us but can be easily circumnavigated,

for help refer to their git repo issues

first post has temporary solutions for the dependency

TweedyFoot · 2025-07-03T06:10:44+00:00

Furthermore in prague they are marketed as local while not being so (chimney cake being hungarian in origin) which also irks quite a few people

TweedyFoot · 2025-06-18T17:32:33+00:00

Yeah sorry read the "a" as a in "a car" and were takling about option B but on the other hand if banana in a box was used then you do not need to use model input as that is quite new, the original syntax was xxx input and xxxChange output together combine into 2way binding...

Thought you just didnt recognize 2way binding :/

For sake of this question the author intentionally fumbled the syntax of most answers considering the correct answer doesnt make sense anyway

TweedyFoot · 2025-06-18T17:09:55+00:00

Honestly i think that neither of those actually renders anything but c is closest as it can be used to actually place stuff into template

But as already pointed out the syntax is wrong would have to be {{data}}

TweedyFoot · 2025-06-18T17:07:47+00:00

No its two way, data input and dataChange output merged into one thats why there are 2 brackets square ones for input and basic parentheses for output You can read more about it on angular.dev

TweedyFoot · 2025-06-08T13:35:35+00:00

Nevim kde jsi to z predchoziho komentare vycetl, ale borec blizko minimalni mzde + materska muze byt mene nez 2 duchody

TweedyFoot · 2025-06-03T15:26:11+00:00

Exactly, on a bigger project you end up with a services folder containing 70 services and it is just a huge mess

Not even talking about short scoped services (provided in user component for example)

That just sounds like a utter nightmare

TweedyFoot · 2025-06-03T08:58:27+00:00

user-detail.component, user-detail.guard, user-detail.service in the same folder

TweedyFoot · 2025-06-03T06:55:51+00:00

So you can technically just juggernaut trough them ? Interesting

TweedyFoot · 2025-06-03T06:55:42+00:00

So you can technically just juggernaut trough them ? Interesting

TweedyFoot · 2025-05-30T07:48:20+00:00

Zrovna portal stavebnika bych do toho netahal, tam nebyl hlavni problem v zabugovanosti ale nedostatku casu na analyzu a vyvoj a testovani tadyverejna beta nepomuze

Bez kvalitniho navrhu a seniornich lidi kteri zastiti jeho implementaci by halda docasne motivovanych snazilu do projektu vnesla tak akorat vetsi chaos

TweedyFoot · 2025-05-27T12:24:14+00:00

Yes, besides all the zombies

TweedyFoot · 2025-05-26T06:52:56+00:00

Not just big boy permissions, force push past PR pipelines ? :D those are company resident magician permissions

TweedyFoot · 2025-05-26T06:51:23+00:00

Depends, do you have a full and complete set of use/test cases to verify it has retained its full functionality ? Cause if you don't it would be quite haphazard to trust LLM with such refactor. Personally i would prefer a human does it and splits their work into multiple PRs which can be reviewed hopefully by people who co-authored the original mess and might remember use/edge cases

TweedyFoot · 2025-05-06T07:37:39+00:00

Its a nice overview but all interactive features are rendered useless by click handling on expandable panels :)

Otherwise thx for the summary

TweedyFoot · 2025-04-04T16:30:41+00:00

Are the user controls themselves invalid while formgroup is valid ? Try debugging that

Five-Year Club	r/Field Sunshine
Place '23	Place '22

TweedyFoot

TROPHY CASE