Skip to content

Week of June 15#479

Merged
duglin merged 1 commit into
xregistry:mainfrom
duglin:June15
Jun 20, 2026
Merged

Week of June 15#479
duglin merged 1 commit into
xregistry:mainfrom
duglin:June15

Conversation

@duglin

@duglin duglin commented Jun 12, 2026

Copy link
Copy Markdown
Contributor
  • add support for "matchversions" (and add to schema spec's model)
  • make "constraints.equals" use "matchcase" when doing string compares
  • clarity that setting maxversions=1 when there are sticky versions -> error
  • tell people who to require sticky versions (set defaultversionsticky'e enum/default to "true")

Fixes #478
Fixes #477

@duglin
duglin force-pushed the June15 branch 3 times, most recently from ed735ee to 7a4d27a Compare June 12, 2026 17:20
@duglin duglin mentioned this pull request Jun 12, 2026
@duglin
duglin force-pushed the June15 branch 4 times, most recently from ffc8c23 to 248ae01 Compare June 17, 2026 14:35

@jskeet jskeet left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

A few small comments, but fine as far as I understand it...

Comment thread core/model.md Outdated
### `attributes.<STRING>.matchversions`
- Type: Boolean.
- OPTIONAL.
- Indicated whether all Versions of a Resource instance MUST have the same

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
- Indicated whether all Versions of a Resource instance MUST have the same
- Indicates whether all Versions of a Resource instance MUST have the same

(I expect, anyway. It's odd to be in the past tense.)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Comment thread core/model.md
- Are statically defined. Meaning, not defined as part of a `ifvalues` clause
or via a `*` extension definition
- Are not defined within an array or map. Within an object is allowed.
- In the case of the attribute type being a `string`, the comparison MUST take

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

As in, if matchcase is false, then it's okay one version to have a value of "ABC" and another to have a value of "abc" without any errors being generated?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes. Do you think I need to be more clear/verbose on that?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Nope, I think it's fine - just thought I'd double-check, as if it didn't mean that, we'd need to be clearer :)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Perfect! Thanks SOOOO much for the quick review!

Comment thread core/spec.md Outdated
```

Likewise, forcing all Resource instances to have "sticky" Versions MAY be
done via the same mechanism but using `true` instead of `false` in the

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
done via the same mechanism but using `true` instead of `false` in the
achieved via the same mechanism but using `true` instead of `false` in the

Maybe? It just feels a little more spec-suitable than "done".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done :-)

@duglin
duglin force-pushed the June15 branch 3 times, most recently from d4a8afd to ac43694 Compare June 17, 2026 18:23
- make 'constraints.equals' use 'matchcase' for strings
- clarity that setting maxversions=1 when there are sticky versions -> error
- tell people who to require sticky versions

Signed-off-by: Doug Davis <duglin@gmail.com>
@duglin

duglin commented Jun 20, 2026

Copy link
Copy Markdown
Contributor Author

Approved off-line

@duglin
duglin merged commit a93053d into xregistry:main Jun 20, 2026
2 checks passed
@duglin
duglin deleted the June15 branch June 20, 2026 17:03
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.

is "constraints" really what we want to use instead of "consistentformat" ? is "equals" case insensitive for strings?

2 participants