anyway I had been waiting for a while to gather more changes to put into a single PR but I wasn't finding anything else so this small PR will have to do for now #310
some of the examples in documentation still bother me because you can't really get away that easily when a function returns a Maybe, but that's for someone more knowledgeable (and less lazy) to fix
because although rare, there's definitely a few edge cases with Feather icons where you'd want to modify the viewBox
but it's not impossible
although I wouldn't know how reasonable such a thing is in the context of SPAs
@html would be sepearate for sure
but I'd be okay with that, yeah
notice the different function used in the example https://www.mint-lang.com/api/modules/Dom#getElementBySelector
that's still in master
like "Into Mint" or something
for example in this
Function(a, b, a) the two a is the same type
it is like type template? just like List<T>
Event attributes should match a specific type signature Function(Html.Event, a) which means that only functions which take an Html.Event and return something can be passed to these attributes.
to explain this a bit more: these type variables come in when you want to specify the behaviour of a function
fun map (func : Function(a, b), array : Array(a)) : Array(b) {
all
as are the same type and all bs are a different type
So versatile.
Thank you.
:+1: