-
Notifications
You must be signed in to change notification settings - Fork 113
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
chore: adding versioned directory(v0 and v1) #319
base: main
Are you sure you want to change the base?
chore: adding versioned directory(v0 and v1) #319
Conversation
✅ Deploy Preview for circuitverse ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
ESLint found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
// const { activeCircuit } = toRefs(simulatorStore) | ||
name = name || 'Untitled' | ||
name = stripTags(name) | ||
scopeList[id].name = name |
Check warning
Code scanning / CodeQL
Prototype-polluting assignment Medium
user controlled input
scope.backups[scope.backups.length - 1] !== backup | ||
) { | ||
scope.backups.push(backup) | ||
scope.history = [] |
Check warning
Code scanning / CodeQL
Prototype-polluting assignment Medium
user controlled input
) { | ||
scope.backups.push(backup) | ||
scope.history = [] | ||
scope.timeStamp = new Date().getTime() |
Check warning
Code scanning / CodeQL
Prototype-polluting assignment Medium
user controlled input
*/ | ||
function loadModule(data, scope) { | ||
// Create circuit element | ||
var obj = new modules[rectifyObjectType(data.objectType)]( |
Check failure
Code scanning / CodeQL
Unvalidated dynamic method call High
user-controlled
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! Do you think we should name it v1 v2 instead of v0 v1?
Since the Vue simulator isn't released yet, it might be better to use v0 as the pre-release version. |
Sounds good.
…________________________________
From: Aryann Dwivedi ***@***.***>
Sent: Wednesday, June 19, 2024 12:35:39 PM
To: CircuitVerse/cv-frontend-vue ***@***.***>
Cc: IMT2019518 Ruturaj Mohite ***@***.***>; Mention ***@***.***>
Subject: Re: [CircuitVerse/cv-frontend-vue] chore: adding versioned directory(v0 and v1) (PR #319)
Looks good! Do you think we should name it v1 v2 instead of v0 v1?
Since the Vue simulator isn't released yet, it might be better to use v0 as the pre-release version.
—
Reply to this email directly, view it on GitHub<#319 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM3ZIZTL333RALKIW4GKKVTZIEUUHAVCNFSM6AAAAABJOPTOD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZXHEYDKOBSGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
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.
LGTM👍
Fixes #320
Describe the changes you have made in this PR -
Versioned Directory Addition
v0
andv1
) with their respectivesrc
folders.Screenshots of the changes (If any) -
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.