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

Shorten the object parts #1

Closed
zalmoxisus opened this issue Dec 13, 2018 · 4 comments
Closed

Shorten the object parts #1

zalmoxisus opened this issue Dec 13, 2018 · 4 comments

Comments

@zalmoxisus
Copy link

When there's lot of data, the tooltip becomes unusable, so would be nice to show at least a part of it as a preview.

Basically we'll need to shorten: when a string is long, object keys or an array length exceeds a certain value.

@romseguy what do you think of moving it to redux devtools monorepo so we can get more attention for contributors?

@romseguy
Copy link
Owner

Sure, do I have to give you access?

@zalmoxisus
Copy link
Author

zalmoxisus commented Dec 13, 2018

Thanks @romseguy! I need only access to npm packages to maintain the same names instead of creating new ones. Then after I transfer the code, I'll send a PR here just adding to the README that this repository is merged and maintained in redux-devtools monorepo. I'll add credits to the README there about it being moved from here. I'd need access also for the other 3:

For the first 2, I'm sorry that I wasn't active when the decision about moving happened, and causing extra-work. I think the right way would be to move them back to you and maintain inside monorepo as well. Not sure if you have access for doing that. I'll open an issue in redux-devtools-chart-monitor to ask the others of you think the same.

@romseguy
Copy link
Owner

You should have received the invite for these 4 packages. I don't need access to the monorepo since I'm not interested in maintaining the chart monitor and its dependencies anymore.

@zalmoxisus
Copy link
Author

Thanks! I moved d3tooltip and map2tree, added credits in the README. Opened this issue there.

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

2 participants