-
Notifications
You must be signed in to change notification settings - Fork 748
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
Add support for repository alphanumeric autolinks (Fixes #1270) #1314
Add support for repository alphanumeric autolinks (Fixes #1270) #1314
Conversation
Type: schema.TypeBool, | ||
Optional: true, | ||
ForceNew: true, | ||
Default: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is_alphanumeric is optional in the API and defaults to true
Hi @kfcampbell, this is ready for review, thanks! |
@douglascayers I see this makes the (breaking) change of switching between In my perfect world, it might be best to remove that functionality, add this feature, and then in a separate breaking change switch the delimiter. Do you think that's too much trouble? Alternately, I could cut v6.0.0 of the plugin and take this change wholesale. |
@kfcampbell Good catch on the breaking change.
❓ Are there other PRs you'd like to merge into the 5.x.x line before cutting the 6.x.x version? If yes, I'm happy to split this PR into two to accommodate. If you're thinking you'll merge both PRs right after each other and end up on the 6.x.x version anyways without other changes in the 5.x.x line, perhaps we just go forward with this one PR? 🤔 |
👍 I had hoped to merge a few other PRs to v5.x.x for small features and dependency updates and (again in my perfect world) do something to address #980 finally, though that item doesn't have to be a blocker for the delimiter change. If you could split it into two PRs, that would be awesome! |
I've converted this to draft while I work on that, thanks |
Thank you! |
Hi @kfcampbell, this is ready for review, thanks! Per your feedback, I've reverted the import syntax changes to avoid introducing a "breaking" change that would prompt a major version change. If I revisit standardizing the import syntax for resources, I'll do that in an isolated PR for as many resources as I can update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@douglascayers awesome, thank you so much! I'll get this released shortly.
I love the idea of standardizing on the import syntax and would happily review future PRs in this direction.
…#1270) (integrations#1314) * Add `is_alphanumeric` for repo autolinks * Test `is_alphanumeric` for repo autolinks * Use parseTwoPartID util func for consistent import ids * Update docs about `is_alphanumeric` and import format * revert import state parsing to avoid breaking change * revert import state parsing to avoid breaking change * revert import state parsing to avoid breaking change
…#1270) (integrations#1314) * Add `is_alphanumeric` for repo autolinks * Test `is_alphanumeric` for repo autolinks * Use parseTwoPartID util func for consistent import ids * Update docs about `is_alphanumeric` and import format * revert import state parsing to avoid breaking change * revert import state parsing to avoid breaking change * revert import state parsing to avoid breaking change
Changes
is_alphanumeric
property of autolinks (available per Add alphanumeric param to AutolinkOptions google/go-github#2450)Tests
github/resource_github_repository_autolink_reference_test.go
is_alphanumeric
property is not set (uses default) or is set to eithertrue
orfalse
How to Test
Create a personal access token with the following scopes:
repo
,admin:org
, anddelete_repo
.Test Output
Usage
Example configuration: