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

Added typescript and update old dependencies to React v.18 #237

Open
wants to merge 21 commits into
base: master
Choose a base branch
from

Conversation

oleg-yasenytsky
Copy link

No description provided.

@AlecDusheck
Copy link

Thanks alot for doing this <3

@wesmorishita
Copy link

Any chance this could be reviewed and merged in?

Copy link

@ffdfo ffdfo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great

@alexschultz
Copy link

@seveibar any chance you can look at this?

@seveibar
Copy link
Contributor

seveibar commented Aug 6, 2024

Hey guys, taking a look

@@ -0,0 +1,7 @@
# Default ignored files
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's remove all the .idea files and add the .idea directory to .gitignore

@@ -1,3 +1,3 @@
{
"semi": false
"semi": true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why change this?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I accidentally changed it, i will fix it

@@ -1,12 +1,15 @@
# React Image Annotate

[![npm version](https://badge.fury.io/js/react-image-annotate.svg)](https://badge.fury.io/js/react-image-annotate)
[![npm version](https://img.shields.io/npm/v/@idapgroup/react-image-annotate.svg)](https://www.npmjs.com/package/@idapgroup/react-image-annotate)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can basically remove the README changes here

"start": "react-scripts start",
"test": "react-scripts test",
"eject": "react-scripts eject",
"storybook": "start-storybook -p 9090 -s public",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm removing storybook means removing a lot of tests, is there any way to keep the stories and upgrade storybook? I'm worried that we've basically lost all of our tests.

If storybook isn't your vibe, we could use react cosmos or ladle, but I think keeping the stories (which are essentially tests) will help me make sure that nothing broken.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't have time for update story book and check tests(

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe in future i will update storybook too

Copy link
Contributor

@seveibar seveibar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm generally supportive of migrating this project to Typescript, I exclusively use Typescript now, also supportive of adding people as maintainers to this project since I don't actively use it.

It's not really possible for me to test these changes because the "stories" code, has been removed. The stories are essentially tests

@AlecDusheck
Copy link

AlecDusheck commented Aug 6, 2024

Would it be possible to toss this in a branch as-is and add a note in the README saying experimental React 18 support is a work in progress?

@oleg-yasenytsky
Copy link
Author

If anyone need package with this pull, i deploy it npm.js
https://www.npmjs.com/package/@idapgroup/react-image-annotate

@seveibar
Copy link
Contributor

seveibar commented Aug 8, 2024

Would it be possible to toss this in a branch as-is and add a note in the README saying experimental React 18 support is a work in progress?

I'm eager to merge this, but I think my comments are pretty reasonable, for a project this old its good to make sure you don't lose testing surface area, and some of the other changes would misdirect the user, eg the README wouldn't link to user to the npm package published by this repo.

To clarify: I'm very eager to merge and make people maintainers

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

Successfully merging this pull request may close these issues.

7 participants