Skip to content

specify required fields #4

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

Merged
merged 2 commits into from
Aug 2, 2021
Merged

specify required fields #4

merged 2 commits into from
Aug 2, 2021

Conversation

drewdaemon
Copy link
Contributor

The API gives us the ability to specify only a subset of dataset info to come back over the wire. This PR takes advantage of that to reduce data transfer overhead.

@drewdaemon drewdaemon requested a review from rgwozdz July 29, 2021 22:03
import { version } from '../package.json';
import { getDataStreamDcatAp201 } from './dcat-ap';
import * as config from 'config';
import { requiredFields } from './dcat-ap/dcat-dataset';
Copy link
Member

Choose a reason for hiding this comment

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

So the required fields stay the same across all requests?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's right. Right now the dependencies are not configurable and this is the comprehensive list.

@drewdaemon drewdaemon merged commit bd15617 into main Aug 2, 2021
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