Skip to content

Document additional JOIN ON conditions - #1573

Open
zw963 wants to merge 1 commit into
luckyframework:mainfrom
zw963:main
Open

zw963 wants to merge 1 commit into
luckyframework:mainfrom
zw963:main

Conversation

@zw963

@zw963 zw963 commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@jwoertink jwoertink left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There's a few unrelated changes sneaking in here. Let's keep the PR strictly to just documenting the JOIN stuff, and leave all of the ameba changes as they were. Those can be updated in a future PR

Comment thread shard.yml
version: ~> 0.10.0
ameba:
github: crystal-ameba/ameba
version: ~> 1.5.0

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is an unrelated change to the PR. Please revert this change

Comment thread .github/workflows/ci.yml Outdated
Comment on lines +21 to +22
- name: Build Ameba
run: crystal build -o bin/ameba lib/ameba/bin/ameba.cr

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is an unrelated change. Let's remove this.

@zw963

zw963 commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor Author

done,

IIRC, ameba 1.5 will failed, but not related to this PR.

In src/ameba/tokenizer.cr:88:15
 88 | lexer.next_string_array_token

I will create a new PR to cherry pick reverted changes.

@jwoertink jwoertink added the guides:next_release Wait until next release for these guides label Oct 26, 2026
@zw963

zw963 commented Oct 28, 2026

Copy link
Copy Markdown
Contributor Author

Should I waiting 有 force merge this PR first and then create a new PR to fix ameba, or do it the other way around?

@jwoertink

Copy link
Copy Markdown
Member

@zw963 I can't merge this until after the next release, so this PR will be sitting for a while. If you'd like to do a separate PR for the ameba, I would be ok with that. But also not necessary. I'm ok merging this PR as-is when it comes time for that.

@zw963

zw963 commented Oct 29, 2026

Copy link
Copy Markdown
Contributor Author

Okay, I created #1574,it has already been done before anyway.

If consider helpful, you can merge.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

guides:next_release Wait until next release for these guides

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants