Open
Conversation
PaulKalho
force-pushed
the
issue-265/table-name-logic
branch
from
1886a11 to
a887315
Compare
PaulKalho
force-pushed
the
issue-265/table-name-logic
branch
from
a887315 to
f08ca5d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Table names are now in this schema:
{project_name}_{input_or_output_name}_{block_custom_name}project_namehas a maximum of 30 chars,block_custom_name15 chars andinput_or_output_namewill be, if necessary, shortened so that the string is below 63 chars in total.Sorry for all the fixer changes.
Closes #265
BTW: There was no need for changes inside the SDK