Skip to content

Making 'max' tag optional#252

Merged
richiware merged 1 commit intomasterfrom
hotfix/#245
Sep 4, 2018
Merged

Making 'max' tag optional#252
richiware merged 1 commit intomasterfrom
hotfix/#245

Conversation

@MiguelCompany
Copy link
Copy Markdown
Member

This fixes #245 making domains->id_range->max optional on the governance file

@MiguelCompany MiguelCompany requested review from richiware and removed request for richiware September 4, 2018 06:08
@MiguelCompany MiguelCompany added the needs-review PR that is ready to be reviewed label Sep 4, 2018
@mikaelarguedas
Copy link
Copy Markdown
Contributor

Thanks @MiguelCompany @richiware !

It looks like the case where only the max tag is specified is still failing, I ticketed the follow-up at #255

julionce pushed a commit that referenced this pull request Sep 11, 2018
richiware pushed a commit that referenced this pull request Sep 13, 2018
* Refs #3271. Hotfix Github #245 Parser fails on id_range if 'min' tag present but not 'max' tag (#252)

* Refs #3139. Added topic profile support.
JuanCarlos-Arce pushed a commit to clearpathrobotics/Fast-RTPS that referenced this pull request Oct 16, 2018
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.

[XMLPARSER] Parser fails on id_range if 'min' tag present but not 'max' tag

3 participants