So we're using a plugin for our framework that uses components to act as wrappers for Bootstrap. Cool.
So, if I do (what ensues is pseudocode/pseudo-markup)
{{NavBar}} // from bootstrap plugin
{{Nav.BarItem}}
<!-- some HTML --!>
{{/NavBar.Item}}
{{/NavBar}}
you get a navbar with convenient bootstrapped styling, nice.
BUT, for some GODFORSAKEN reason, if I turn <!-- some HTML --!> into a component:
{{NavBar}}
{{NavBar.Item}}
{{MyComponent /}}
{{/NavBar.Item}}
{{/NavBar}}
it doesn't work???????? But I need to write this component because the senior dev wants to reuse the code I'm using in other places too? SO I NEED TO HAND-CODE THE BOOTSTRAP CSS ENTIRELY MYSELF??????????????????????????????????
@aescling !important
@aescling chimkin
re: incest; poll
@Lady I actually knew about the infamous Folgers but I didn't think to make the connection here in this context
@aescling not sure
@aescling TOMORROW
@aescling was this low-key a roast 💀
@aescling No exceptions.
kept afloat by big ideas.
you can call me Caleb or Clodsire. i also go by clodboy and catwin. i am not picky about names (unless its one amy made up)
videogame enjoyer. mathematics hobbyist and recovering physicist. software engineer. professional wonk. prophet of The Truth. the walking embodiment of "not diagnosed, but somethings wrong". i like animals that wear cowboy hats.
pfp is by @The_T
header is by @vaporeon_
"i regret ever allowing him here" ~aescling
"oh you're one of those weird movie likers" ~Ti
"i know your taste in movies well enough to discount your opinion" ~globin
"caleb is the only person on this websites who truly understands what the report button is for: 'i don't like this post'" ~holly
30+
straight
he/him