-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
🔧 wip: nuxt3 #6917
🔧 wip: nuxt3 #6917
Conversation
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Reviewpad Report
|
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.
The PR diff size of 17895 lines exceeds the maximum allowed for the inline comments feature.
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.
The PR diff size of 27387 lines exceeds the maximum allowed for the inline comments feature.
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: @nuxt/[email protected], [email protected], [email protected] |
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
Hey, is insider trading allowed, what do you think |
maybe @stephenjason89 😄 |
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.
The PR diff size of 28833 lines exceeds the maximum allowed for the inline comments feature.
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.
The PR diff size of 24513 lines exceeds the maximum allowed for the inline comments feature.
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.
The PR diff size of 24541 lines exceeds the maximum allowed for the inline comments feature.
Good job @roiLeo, It's 12midnight here. If you need help just let me know. My tg handle is SOW89 |
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.
The PR diff size of 24077 lines exceeds the maximum allowed for the inline comments feature.
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.
The PR diff size of 20746 lines exceeds the maximum allowed for the inline comments feature.
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.
The PR diff size of 20768 lines exceeds the maximum allowed for the inline comments feature.
What's the strategy for merging this? You want to do page by page or do some nuxt layout? |
Wait for some issue to be resolved, I can handle conflicts & push from others (fork my repo)
From #2690 (comment) I've done:
We need to fix some packages config now. @stephenjason89 have you made some progress on I18n plugin? |
@roiLeo, it seems like we can use a proxy to gradually release it to the user page by page. Maybe we can start with
I think this is the major one
this one can't be solved with just a fork? |
@roiLeo, but if you prefer not to use a proxy, we can stick with this way
Are there any changes that need to merge in |
nuxt/content doesn't work on
wdym? I want to use it like it's on Doc (
I'd rather not
Idk if |
So I can create a new chief issue for migration and replace this one? To not break our current flow and keep a flawless release cycle, I would propose making Later we can still back merge new things and once it is even 1:1 lmk and I can proceed. Hanging out in one PR for this major upgrade is not so good I think. |
Yes please! could you push your code to my repo? |
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.
The PR diff size of 20806 lines exceeds the maximum allowed for the inline comments feature.
IMO, it's better that someone (Kodadev insider) handle the migration, it would be less exhausting than having to go through multiple reviews and better to resolve conflicts.
Yes! Once we fix oruga (programmatic) & apollo config, we could be able to release an alpha branch.
why that? note: not happening before 01/09 sorry |
@roiLeo |
Would you like to check/fix a component, a page or a plugin? Just let me know wich part you want to work on. |
component/page please |
Try first with something easy/doable like spotlight, series-insight, assets page then push on my repo and I'll merge it as quickly as I can (if it's working) edit: 📔 To anyone going to work with page/component that use
const { result: res } = useQuery(query, variables)
const res = ref()
const { onResult } = useQuery(query, variables)
onResult((result) => (res.value = result.data))
const res = ref()
const fetchData = async () => {
const { data } = await useAsyncQuery(query, { ...variables })
res.value = data
} |
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.
The PR diff size of 20842 lines exceeds the maximum allowed for the inline comments feature.
Code Climate has analyzed commit 392bf0b and detected 0 issues on this pull request. View more on Code Climate. |
SonarCloud Quality Gate failed. 1 Bug No Coverage information Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
I've made
This and because the process is not around the KodaDot branch in this repository and we can split load among others, not make you block migration by single dev on resolving conflicts. Hopefully, you understand. Rather encourage split tasks in For others likewise, making it against |
|
@kodadot/code-review-guild I'm stuck on some build errors if anyone want to try out feel free to checkout this branch