The button component is going to be based on the decision we made in #87 .
the component function changes based on it's type property and it's parent container.
Wat deze ticket omvat
Onderzoek ( what the best way is to build this component).
Standards & conventies
Taken
Otwikkel component
Links and information that could be useful while building the component
Test
Onderzoek
How did you come to this code or aesthetical decision
for this component, I used the following as research
Morphological chart
standards & conventions #4
[ ] Zoveel mogelijk werken met de atomic components methode (DRY)
[ ] Mobile First
[ ] Comments toevoegen aan complexe code zodat dit voor iedereen in de squad te begrijpen is
[ ] Kebab case
[ ] Responsive
[ ] Progressive enhancement
[ ] Toegankelijk
Taken
[ ] component should pass data to it's parent
[ ] container queries implementation
[ ] it should be programmable to have different type (plain button , link ,submit button, route button )
[ ] aesthetical properties can be adjusted outside of the component
Beschrijving
The button component is going to be based on the decision we made in #87 . the component function changes based on it's type property and it's parent container.
Wat deze ticket omvat
Onderzoek
standards & conventions #4
Taken
Ontwikkeling
Links & Referencies
Test
How to execute the tests
Test resultaten
Oplossing