Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

State of the project? Docs discrepancies. Version 5.4.5 vs 6.0.0 #479

Open
cristian-eriomenco opened this issue Dec 16, 2020 · 3 comments
Open

Comments

@cristian-eriomenco
Copy link

cristian-eriomenco commented Dec 16, 2020

I've noticed a lot of discrepancies between the docs and sandboxes.

The react-id-swiper doesn't seem to work properly (coverflow, nav buttons) with any version of swiper past 5.4.5. Yet the docs state:

npm install react-id-swiper@latest swiper@latest
and
import 'swiper/css/swiper.css'; - this file doesn't exist
instead it should be :
import "swiper/swiper-bundle.min.css";

There are some PRs which are sitting there for a while now.

Swiper itself seems to have bundled react support in itself: https://swiperjs.com/react/

Long story short is the project abandoned?

@claudiopedrom
Copy link

Same doubt here.

@bbaki
Copy link

bbaki commented Mar 17, 2021

Seems abandoned to me. I'm not quite sure what was the purpose of this project anyway. Seems like a react wrapper for swiper but as you have pointed out, swiper seems to support react out of the box so is there any other reason for this project?
Woud be cool however to have an official info on this.

@ItsTarik
Copy link

Agree, very odd .. i think this packages is helping with swiper custom builds, Swiper alone has some issues for example using it along with nextjs the dev build or on resizing the screen causes some odd behaviors, I'm trying to use this packages so maybe those issues will disappear but i agree, since swiper.js is already exporting react primitives already there is no sense having this package also swiper.js 7.0.0 is changing its core implementation and i found it also confusing that is supporting just esm modules !!
That's very confusing for the community, is there someone to give a clear explanation about all these stories ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants