Skip to content

fix: organizationUnitName is prohibited#903

Merged
christopher-henderson merged 3 commits intozmap:masterfrom
XolphinMartijn:noOU
Dec 16, 2024
Merged

fix: organizationUnitName is prohibited#903
christopher-henderson merged 3 commits intozmap:masterfrom
XolphinMartijn:noOU

Conversation

@XolphinMartijn
Copy link
Copy Markdown
Contributor

A fix for #902, which had the prohibited OU field included in the allow list

@XolphinMartijn XolphinMartijn changed the title fix: organizationUnit is prohibited fix: organizationUnitName is prohibited Dec 9, 2024
Copy link
Copy Markdown
Member

@christopher-henderson christopher-henderson left a comment

Choose a reason for hiding this comment

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

Gosh, the wording/layout of this section is confusing. You have to be very careful to notice that this is the only field that is prohibited.

Looks good to me. Just please update the integration tests. The following one-liner ran from zlint/v3 will run this lint on the corpus and update the expectations file.

make integration INT_FLAGS="-overwriteExpected -lintFilter='e_ev_extra_subject_attribs'"

@XolphinMartijn
Copy link
Copy Markdown
Contributor Author

@christopher-henderson Thanks! I had missed the integration-test failure notice

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