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
React Images v1 🎉 #199
Comments
Congrats! Which build systems have you considered so far. |
It would benefit testing if v1 could be published to npm with a beta or alpha version number and the |
@jossmac Is there a way we can help test this? What is the recommended way to use the Super excited about this! 🎉 |
UpdateCheckout the demo site: v1 Demo --> Alpha releases of yarn add react-images@next |
Hi @jossmac,
I'm not seeing the examples at the bottom of the page...
…On 19 February 2018 at 10:44, Joss Mackison ***@***.***> wrote:
Update
Checkout the demo site: v1 Alpha Demo --> <http://bit.ly/react-images-v1>
Alpha releases of ***@***.*** available on npm:
yarn add ***@***.***
CC @jorrit <https://github.com/jorrit> @codeluggage
<https://github.com/codeluggage>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#199 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABs6x80ldn0eJChOs_et_COUk8zXWz0Kks5tWLXcgaJpZM4RvOFb>
.
|
Works ok in Chromium on Linux but not FF. Quick inspection shows that each
thumb in the gallery with class .css-1vnvkj1 has a height of zero.
…On 19 February 2018 at 10:49, Ben Howell ***@***.***> wrote:
Hi @jossmac,
I'm not seeing the examples at the bottom of the page...
On 19 February 2018 at 10:44, Joss Mackison ***@***.***>
wrote:
> Update
>
> Checkout the demo site: v1 Alpha Demo --> <http://bit.ly/react-images-v1>
>
> Alpha releases of ***@***.*** available on npm:
>
> yarn add ***@***.***
>
> CC @jorrit <https://github.com/jorrit> @codeluggage
> <https://github.com/codeluggage>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#199 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABs6x80ldn0eJChOs_et_COUk8zXWz0Kks5tWLXcgaJpZM4RvOFb>
> .
>
|
Not proposing this as a solution but I've just hacked it so it works in FF
by removing position:absolute; from the image class .css-3c3ju2 (might give
you an idea at least)!
…On 19 February 2018 at 10:53, Ben Howell ***@***.***> wrote:
Works ok in Chromium on Linux but not FF. Quick inspection shows that each
thumb in the gallery with class .css-1vnvkj1 has a height of zero.
On 19 February 2018 at 10:49, Ben Howell ***@***.***> wrote:
> Hi @jossmac,
> I'm not seeing the examples at the bottom of the page...
>
> On 19 February 2018 at 10:44, Joss Mackison ***@***.***>
> wrote:
>
>> Update
>>
>> Checkout the demo site: v1 Alpha Demo -->
>> <http://bit.ly/react-images-v1>
>>
>> Alpha releases of ***@***.*** available on npm:
>>
>> yarn add ***@***.***
>>
>> CC @jorrit <https://github.com/jorrit> @codeluggage
>> <https://github.com/codeluggage>
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub
>> <#199 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/ABs6x80ldn0eJChOs_et_COUk8zXWz0Kks5tWLXcgaJpZM4RvOFb>
>> .
>>
>
>
|
@benhowell cheers mate, fixed now! Also added prop type documentation 💃 |
Wha about this? You define array of images in doc in this way. You duplicate key. |
@codeluggage @damienbrz @weslleyaraujo the files should be on NPM now |
@neptunian should the version be |
@kachkaev you're right, i'll fix that |
@neptunian Unfortunately, the |
@neptunian just installed the alpha version and the lib folder is not there. |
I get the following warnings when adding react-images@next:
Have these packages been upgraded recently? |
|
Unfortunately, SSR is still not working (see #247 for further details). |
Ran into the SSR issue with Netlify as well. Edit: In the meantime, I just used patch-package to add a few checks in Here are the file patch contents:
|
@jossmac @neptunian what about version 1?there is some plan to release that? it's still 0.5.19 . tnx! |
@jossmac @neptunian |
unless there are any major issues with v1 i'd be happy to release it if @jossmac is okay with it. I'm not sure Flow was the best decision over Typescript for typing but, perhaps that could be changed later. What does everyone think? The only major issue that anyone seems to have brought up is the SSR issue which looks like an easy fix. |
@jossmac @neptunian Will the SSR issue be fixed any time soon? It would be great if v1 could be released with SSR support. |
@iammatthias |
Is there any plan to released this version ? I feel like nobody is taking care of this library anymore. |
You right, no one cares about this library. |
@OriAmir There hasn't exactly been any PRs to fix any issues with this so it wouldn't make much of a difference. If someone would like make a PR for the SSR issue, that would be welcome. Otherwise I'll have to get it to when I get a chance which should be soonish! |
@neptunian |
@OriAmir the SSR issue affects a lot of people who might use this library, considering how popular frameworks like Gatsby are becoming. If you want the current version released as a V1, what’s stopping you from using the alpha? Changing it from alpha to V1 doesn’t make any functional difference. Give the maintainers time to do their thing and live their lives. The great thing about this project being open-source is that nothing is stopping you from submitting a PR that fixes what you perceive to be an issue. @neptunian, thanks for the work you’ve put into this. |
if you install the latest next version (react-images@next), the SSR issue should be fixed. let me know if there are any issues and then we can see about finally moving to v1! |
I want to mention before the release of v1 that I do not plan to maintain v0.x. I can create a branch for it, if anyone else wants to work on it, and accept PRs there. |
@neptunian Thank you for the amazing work! And everyone here as well |
For the past few months I've been rewriting
react-images
from the ground up. Having solidified some of the core concepts, i'd really like to hear your thoughts 🙂The main impetus for rewriting this library was providing consumers with the building blocks necessary to create their component. Need extra buttons in the header? No problem, import react-images'
<Header />
component and enhance it. Need to render videos rather than images? No problem, replace the<View />
component and pass the data required to theviews
property.General notes:
create-react-app
until we decide on a build setupFeatures of v1:
Many of the requirements, issues, and feature requests should be addressed by the new customisable component architecture without requiring changes to the core.
What this means for v0.x
No need to worry. I, together with @neptunian (the primary maintainer, who's doing an amazing job!), will continue to release critical bug fixes. We won't however be implementing enhancements or new features unless provided in a rock-solid PR.
The new API is a massive departure from v0.x, so there won't be an "upgrade guide" as such. I'll endeavour to provide a handful of examples to cover most use-cases and welcome anyone else to do the same.
Still left to do:
I'd like to thank everyone who has contributed to this project over the years, without your support react-images wouldn't be where it is today. Cheers to the open source community 💖
Looking forward to your feedback!
The text was updated successfully, but these errors were encountered: