-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
feature/multi-element-action #467
Conversation
I did some tests here and it's working smoothly.
|
Bumps [jsonwebtoken](https://github.com/auth0/node-jsonwebtoken) from 8.5.1 to 9.0.0. - [Changelog](https://github.com/auth0/node-jsonwebtoken/blob/master/CHANGELOG.md) - [Commits](auth0/node-jsonwebtoken@v8.5.1...v9.0.0) --- updated-dependencies: - dependency-name: jsonwebtoken dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
…webtoken-9.0.0 Bump jsonwebtoken from 8.5.1 to 9.0.0
- Ex: v3.x.x -> v4.x.x - Also, define type for children at Button.tsx to ANY
Need after update @types to newer version
Update to match devDependencies versions and avoid breaking changes As we currently have after I merge my last pull request ¯\_(ツ)_/¯
|
@miltonbsn regarding the limitation to copy + paste in Logic models, I have the following question: Considering Foreign key as the limitation factor, can we enable c+p if a table still don't have stablished relationships yet? |
Copy update.
app/i18n/languages/en.js
Outdated
'Copy and paste is not allowed on this module due to complexity when updating references': 'Copy and paste is not allowed on this module due to complexity when updating references' |
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 this copy being used?
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.
Good catch! It was my first version but found too long, changed and forgot this here.
The new one will be:
EN: Copy is not allowed on this module when element has references.
PT-BR: Copiar não é permitido nesse módulo quando elementos já estiverem conectados.
What do you think?
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.
Looks good to me. Will you update it here or in a new branch?
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.
Here, I am working on it right now. Let's try merge this today.
On more thing... Branch name is |
Yesss, I was a bit lazy but will do it 😅 |
Yes, I started doing one thing and had this idea and delivered two. Sorry and forgive me this time 🙏 |
@idmarjr we are good to go again. I did a mistake when updating this branch but i will fix when merging this PR. |
@idmarjr wait, it is worst than I expected, i will open another PR |
Summary
Copy and paste allowed only on conceptual module.
Logic relations have deep internal connections (AKA foreign key), to copy and paste elements we have to update all these references and although not impossible, it is very complex and could lead to bugs.
In order to inform users about this limitation, the following message is now visible when users try to copy + paste elements in a logic model
Unrelated fixes
Close #456
Close #473