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

@href on a c:manifest/c:entry must become mandatory #150

Open
eriksiegel opened this issue Jun 27, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@eriksiegel
Copy link
Contributor

commented Jun 27, 2019

Given the decisions we made on #116, the c:entry/@href attribute must become mandatory. At least, I don't see the meaning or possible usage of a c:entry without an @href.

However, where the master schema resides and therefore how this must be done is beyond my current understanding.

@ndw

This comment has been minimized.

Copy link
Collaborator

commented Jun 27, 2019

I've pushed a PR to make the href attribute required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.