Closed prachi00 closed 1 year ago
Name | Link |
---|---|
Latest commit | 331c471dd137773cff37c6867a036ef9fd773318 |
Latest deploy log | https://app.netlify.com/sites/koda-canary/deploys/64765187e08abe00080a625e |
Deploy Preview | https://deploy-preview-5870--koda-canary.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Reviewpad Report
:warning: Warnings
@prachi00 can you provide screenshot pls?
SS
@prachi00 can you provide screenshot pls?
added some
@prachi00 can you please resolve conflicts?
@prachi00 can you please resolve conflicts?
done
Agree with @roiLeo
@kodadot/qa-guild is it possible to check this ? Seems quite a big change πΆ
please could you check
type="is-...
=>variant="..."
- remove
message
prop on NeoField
why are we removing message props? it seems it is supported by oruga https://oruga.io/components/field.html#props @roiLeo
@prachi00 can you resolve conflicts please?
@kodadot/qa-guild is it possible to check this ? Seems quite a big change πΆ
will do
some test cases are failing after resolving conflicts, I'll fix them tomorrow
Hi @prachi00 is it possible to still make a little change ? I am not sure how it behaves rn but ideally have it like this for light and dark:
@preschian @roiLeo test cases are failing for this part when updating to neoInput, but it seems like we dont even use this function, can we remove it? can someone confirm?
test cases are failing for this part when updating to neoInput, but it seems like we dont even use this function, can we remove it? can someone confirm?
checking
test cases are failing for this part when updating to neoInput
@prachi00 I think we can use vue.extends
instead. if we want to add .neo-*
specific class, use vue.mixins
and then forked rootClasess()
from OInput
code for NeoInput.vue
using mixins
<script>
import { OInput } from '@oruga-ui/oruga'
// https://github.com/oruga-ui/oruga/blob/develop/packages/oruga/src/components/input/Input.vue
export default {
mixins: [OInput],
computed: {
rootClasses() {
return [
'neo-input',
this.computedClass('rootClass', 'o-ctrl-input'),
{
[this.computedClass('expandedClass', 'o-ctrl-input--expanded')]:
this.expanded,
},
]
},
},
}
</script>
<style lang="scss">
@import './NeoInput.scss';
</style>
test cases are failing for this part when updating to neoInput
@prachi00 I think we can use
vue.extends
instead. if we want to add.neo-*
specific class, usevue.mixins
and then forkedrootClasess()
fromOInput
code for
NeoInput.vue
using mixins<script> import { OInput } from '@oruga-ui/oruga' // https://github.com/oruga-ui/oruga/blob/develop/packages/oruga/src/components/input/Input.vue export default { mixins: [OInput], computed: { rootClasses() { return [ 'neo-input', this.computedClass('rootClass', 'o-ctrl-input'), { [this.computedClass('expandedClass', 'o-ctrl-input--expanded')]: this.expanded, }, ] }, }, } </script> <style lang="scss"> @import './NeoInput.scss'; </style>
thank you for this, works fine now and tests are clearing as well
@prachi00 checked latest commit, found just few things: General:
Dark mode:
And I have a question about top&bottom padding and line-height (8px as is now looks ok as well, since there is 16px font and height of the field is 48px. Line height is probably the reason there is 8px and not 12px) How exactly is the line-height set as of now? I can see that rn we are using 1.5 rem?
Transfer:
Identity
Collection
Create NFT
Deployed version(Lacking some description at the bottom of it and also the char count):
In case there is any desciptive text lets have it like this. It also done this here: #5939
Also please change the error color to match our red which is #FF5757 (k-red) Either than that error messages can stay as is (under textfield left) until further change.
I think the margin bottom is 12px default by oruga, we can change it though, should we change to 8?
looks like this now
PS, havent made the alignment fix yet as it is using <b-select, and it would be fixed when migrating <b-select to neoselect
@VladoTheBoi @prury
looks like this now
PS, havent made the alignment fix yet as it is using <b-select, and it would be fixed when migrating <b-select to neoselect
@VladoTheBoi @prury
cool! is it the same case for this one?
also:
This happens when i input a number on it:
https://github.com/kodadot/nft-gallery/assets/36627808/b2891908-40bd-40eb-a670-3a79df59e22b
Plus button gets deactivated when there is a form verification pending( it doesn't happen in beta.kodadot.xyz):
https://github.com/kodadot/nft-gallery/assets/36627808/789bc054-bde2-43d9-bd4b-97dfef6a44f3
I think the margin bottom is 12px default by oruga, we can change it though, should we change to 8?
Which margin do you mean exactly?
Deployed version(Lacking some description at the bottom of it and also the char count):
In case there is any desciptive text lets have it like this. It also done this here: #5939
Also please change the error color to match our red which is #FF5757 (k-red) Either than that error messages can stay as is (under textfield left) until further change.
@prachi00 I posted this, not sure you've seen that. Still several things need change:
So few things:
So few things:
- @VladoTheBoi what is missing please open a follow-up issue
- @prachi00 please resolve conflicts and you have some comments from @prury, would love to merge this week
yeah we need to merge, conflicts keep popping up everyday π’
@prury I dont understand the issue with 1st video? is it that usd value is not getting updated? I see it getting updated though so not sure
As for the 2nd one, it seems theres an icon that isnt showing when form is invalid and its taking up all the space @roiLeo @preschian I see that the :before isnt getting applied here to icon from oruga and that is why it isnt showing up currently, would you have any idea why the icon isnt showing up?
for now, I have hidden this class so that the danger icon doesnt show up, we can solve it in another issue as this PR is getting huge
it seems theres an icon that isnt showing when form is invalid and its taking up all the space
there is no icon named alert-circle
on fa https://fontawesome.com/icons/alert-circle?s=solid. could you change to something else?
@prachi00 Watched my video again and its not really showing what i was trying to record, the whole site was jumping/shifting/updating when i typed a number on the amount field, but seems to be fixed now.
The add button on the transfer page is still lacking alignment tho.
I'll fix the add button alignment in the followup issue with other css fixes
it seems theres an icon that isnt showing when form is invalid and its taking up all the space
there is no icon named
alert-circle
on fa https://fontawesome.com/icons/alert-circle?s=solid. could you change to something else?
I didnt add it though, this icon was added by oruga, I'll look into replacing it if we can
fixed the conflicts again, can we merge now, I'll do the rest of styling changes in followup issue @vikiival
@prachi00 can you please open the follow-up issue with changes that needs to be done?
@prachi00 can you please open the follow-up issue with changes that needs to be done?
done
So π₯Ί
So π₯Ί
resolved conflicts again, can be merged now
Code Climate has analyzed commit 331c471d and detected 0 issues on this pull request.
View more on Code Climate.
Also, e2e test cases are failing on main now, I have fixed some of them in this pr by removing it as I think it doesnt exist anymore, I hope that is correct, more are failing but I want to confirm that removing them is the right way to fix it? let me know if I need to revert those changes if we need them, i'll do it π«£ CC @preschian @vikiival @roiLeo
Also, e2e test cases are failing on main now, I have fixed some of them in this pr by removing it as I think it doesnt exist anymore, I hope that is correct, more are failing but I want to confirm that removing them is the right way to fix it? let me know if I need to revert those changes if we need them, i'll do it π«£ CC @preschian @vikiival @roiLeo
PS can we merge this pr now please, as the test cases failing are not related to this anyway
I hope that is correct,
So that means you don't propagate them?
I hope that is correct,
So that means you don't propagate them?
what do you mean propagate?
what do you mean propagate?
What was the reason to remove lines from the tests. And how to bring the back
what do you mean propagate?
What was the reason to remove lines from the tests. And how to bring the back
because they did not exist and thats why they failed, do we even want them back?
Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
π __ Let's make a quick check before the contribution.
PR Type
Context
Before submitting pull request, please make sure:
Optional
Had issue bounty label?
Community participation
Screenshot πΈ
Copilot Summary
π€ Generated by Copilot at e1b9ba3
No summary available (Limit exceeded: required to process 75846 tokens, but only 50000 are allowed per call)
π€ Generated by Copilot at 7b7ed90