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

Get metadata in a human-readable form from loaders #178

Merged
merged 3 commits into from
May 5, 2020

Conversation

keller-mark
Copy link
Member

@keller-mark keller-mark commented May 4, 2020

This PR adds a getMetadata function to both loaders. In the OMETiffLoader the omexml variable is used. In the ZarrLoader an empty object is returned. I am not sure whether the zarr files currently contain information that would match what is available in omexml.

I had to upgrade babel because npm run start threw errors which is why the package.json changed.

@keller-mark keller-mark requested a review from ilan-gold May 4, 2020 23:05
Comment on lines +37 to +41
"@babel/core": "^7.9.0",
"@babel/plugin-transform-regenerator": "^7.8.7",
"@babel/plugin-transform-runtime": "^7.9.0",
"@babel/preset-env": "^7.8.3",
"@babel/preset-react": "^7.8.3",
"@babel/preset-env": "^7.9.0",
"@babel/preset-react": "^7.9.0",
Copy link
Collaborator

Choose a reason for hiding this comment

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

What's up here? Just want to understand.

Copy link
Member Author

Choose a reason for hiding this comment

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

I get this error when running npm run start using the package.json that is currently on the master branch. I think it may be due to the fact that I am on node 14, and it is possibly the same error that @manzt was seeing on travis last week. But upgrading these babel dependencies fixed it.

Screen Shot 2020-05-05 at 9 55 05 AM

Copy link
Member Author

Choose a reason for hiding this comment

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

However, if the package.json and package-lock changes should be in a different PR I can revert them

Copy link
Collaborator

Choose a reason for hiding this comment

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

No it's ok. Let me check this out and test.

@ilan-gold
Copy link
Collaborator

Sorry, meant to approve, not review. Still curious about the comment though.

@ilan-gold
Copy link
Collaborator

Ok, the new babel seems to work for me on 13.

@keller-mark
Copy link
Member Author

Ok great

@keller-mark keller-mark merged commit 165fad4 into master May 5, 2020
@keller-mark keller-mark deleted the keller-mark/get-metadata branch May 5, 2020 14:36
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.

2 participants