Skip to content

feat: Use module name to prevent keyword collision with enum values#1072

Merged
aandreassa merged 2 commits into
mainfrom
module-name-keyword-collision
Apr 25, 2024
Merged

feat: Use module name to prevent keyword collision with enum values#1072
aandreassa merged 2 commits into
mainfrom
module-name-keyword-collision

Conversation

@aandreassa
Copy link
Copy Markdown
Contributor

A slight change from #1061 in order to be compatible with yard. It now uses the module name instead of self.

@aandreassa aandreassa marked this pull request as ready for review April 25, 2024 21:09
@aandreassa aandreassa requested a review from a team April 25, 2024 21:09
@aandreassa aandreassa merged commit dbac2f0 into main Apr 25, 2024
@aandreassa aandreassa deleted the module-name-keyword-collision branch April 25, 2024 21:17
aandreassa added a commit that referenced this pull request May 27, 2026
I previously addressed these keyword collisions in PR #1061 and #1072.

However, the previous  syntax still generates YARD proxy warnings that cause strict builds to fail (i.e. `fail-on-warning`), an issue observed during CI for `google-apps-card-v1`.

This update utilizes `const_set` to successfully bypass the warnings.

I verified directly on the gem via manual edits and running `toys yard`.
aandreassa added a commit that referenced this pull request Jun 4, 2026
I previously addressed these keyword collisions in PR #1061 and #1072.

However, the previous  syntax still generates YARD proxy warnings that cause strict builds to fail (i.e. `fail-on-warning`), an issue observed during CI for `google-apps-card-v1`.

This update utilizes `const_set` to successfully bypass the warnings.

I verified directly on the gem via manual edits and running `toys yard`.
aandreassa added a commit that referenced this pull request Jun 4, 2026
I previously addressed these keyword collisions in PR #1061 and #1072.

However, the previous  syntax still generates YARD proxy warnings that cause strict builds to fail (i.e. `fail-on-warning`), an issue observed during CI for `google-apps-card-v1`.

This update utilizes `const_set` to successfully bypass the warnings.

I verified directly on the gem via manual edits and running `toys yard`.
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