Closed kukac7 closed 7 years ago
Hey @kukac7, it seems like the ^
would be a better option for now.. If Flickity
pushes out a 3.0.0
release it could have breaking changes that this library would need to account for. With the ^
it will allow any Flickity
version until a major release.
Is there a specific use case you were trying to solve with this PR?
@benjamincharity It was the angular about it, but okay. 😃
Sorry, was referencing the wrong library... but ideas stays the same.
Coverage remained the same at 86.881% when pulling 6b0a625180338da3f87212bd99da5fa4d44d4f89 on kukac7:patch-7 into 64ac7d7ce477b063164ed8d8b5f056351c938574 on benjamincharity:master.