Skip to content
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

New PR for margins in stable - fixes #9651 #9982

Merged
merged 16 commits into from
Feb 19, 2018
Merged

New PR for margins in stable - fixes #9651 #9982

merged 16 commits into from
Feb 19, 2018

Conversation

seekheart
Copy link
Contributor

@seekheart seekheart commented Feb 10, 2018

new pr for #9903

Changes

see #9903 screenshots


UUID: 0848ed18-0966-4d90-83da-a1b4ae1500cc

Fixes #9651

@negue negue self-assigned this Feb 10, 2018
Copy link
Member

@negue negue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your PR 👍

Could you please fix the mentioned fixes and revert the changes on:

  • website/static/presskit/Habitica - Gamify Your Life.mp4
  • website/static/presskit/presskit.zip

@@ -22,6 +22,9 @@ div(v-else)
slot(name="popoverContent", :item="item")
</template>

<style>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you remove the empty style tag?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@@ -3,7 +3,7 @@ div
.item-wrapper(@click="click()", :id="itemId")
.item(
:class="{'item-empty': emptyItem, 'highlight': highlightBorder}",
)
).pet-slot
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.pet-slot should be after .item before the attributes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it already is?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you give me a snippet for clarity please?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry what I meant was .item.pet-slot(

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alrighty, I couldn't git revert the two files you requested, is there an easier way?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also for the stuff under .pet-slot lines 7 I left them be.

@seekheart
Copy link
Contributor Author

@negue how do I revert the changes on those files?

@negue
Copy link
Member

negue commented Feb 10, 2018

to revert you can use this

git checkout origin/develop -- PATH/FILE for both mentioned files and then just commit, then those files will have the same content again ^^

@seekheart
Copy link
Contributor Author

does that still apply if I forked the repo?

@negue
Copy link
Member

negue commented Feb 10, 2018

yes it should work too, since HabitRPG/habitica should've been added as remote named origin and origin/develop points to our develop branch

@seekheart
Copy link
Contributor Author

according to the wiki it was named upstream? so still origin or upstream?

@negue
Copy link
Member

negue commented Feb 10, 2018

could you check how your remotes are named? mine still is at origin , maybe I added it myself

@seekheart
Copy link
Contributor Author

it's upstream for me, I can't push the changes in till tmr anywho. I think I nailed everything you wanted. :)

@negue
Copy link
Member

negue commented Feb 10, 2018

ok thank you 👍

@seekheart
Copy link
Contributor Author

seekheart commented Feb 10, 2018

sorry to be a bother @negue I think I just successfully pushed the changes here :)

@negue
Copy link
Member

negue commented Feb 10, 2018

@seekheart yes but now we also need to revert the saving pngs commit, I'd suggest to always use a different branch for fixes / features, not to push it always to develop :)

This reverts commit a38ea66.
@seekheart
Copy link
Contributor Author

all set, thanks for the advice @negue hopefully this is the last thing I need to push xD.... in the future I'll use a feature branch

@negue
Copy link
Member

negue commented Feb 10, 2018

it seems the files are still changed :/ maybe its just easier to create a third PR with only that css change and nothing else. and make you sure branch from upstream/develop not develop(of your local branch) that way you always have the latest changes

@Alys
Copy link
Contributor

Alys commented Feb 10, 2018

@seekheart Can you remove the mp4 and zip file too? They're likely to have been modified in your local install due to a problem that's unrelated to your changes, but you can avoid having irrelevant files included in a PR by committing only the files you changed. E.g., git commit filea fileb rather than git commit -a.

If you're not sure how to remove them, the info at the first couple of links from this search should help.

@Alys Alys changed the title New PR for margins in stable. New PR for margins in stable - fixes #9651 Feb 10, 2018
@seekheart
Copy link
Contributor Author

I think I got it now @Alys the linked help and the two files are gone. @negue only css changes now :D

.pet-progress-bar {
height: 4px;
background-color: #24cc8f;
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you please remove the duplicate css rule?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

duplicate css rule? @negue

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nvm I took care of it ;) @negue

@Alys
Copy link
Contributor

Alys commented Feb 12, 2018

@seekheart Can you also please do the Mounts? The issue mentions them as well and both should be modified together so it doesn't look inconsistent.

@seekheart
Copy link
Contributor Author

@Alys are CSS classes global if I don't have <style scope> declaration? I figured I can just add .pet-slot to mountItem.vue?

@paglias
Copy link
Contributor

paglias commented Feb 12, 2018

Yes, anything not in a <style scoped> slot is global, but in that case for global css it's better to use the assets/scss folder

@seekheart
Copy link
Contributor Author

@Alys @negue pushed the changes to mounts as well.

@@ -15,6 +15,11 @@ div
slot(name="popoverContent", :item="item")
</template>

<style lang="scss">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since this style block is not scoped can you move it to the assets/scss folder?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's also a duplicate of the other change you made so you should just keep one version and move it to assets/scss

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when I move to assets/scss is that going to be a new file and if so how do I call it? Is it called automatically from some build task?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would put it into the existing item.scss file

@seekheart
Copy link
Contributor Author

@paglias @negue it's now in one place under item.scss in assets.

@@ -19,6 +19,10 @@
margin-bottom: 8px;
}

.pet-slot {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just one small change and this should be good to go, can you change the selector from .pet-slot to .item.pet-slot so it's more specific?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@paglias
Copy link
Contributor

paglias commented Feb 19, 2018

@seekheart thanks for this! I'm merging the PR and awarding your contributor tier.

Note that further tiers require increasing amounts of work from one to the next, so Tier 2 may require a couple of PRs or a larger PR to attain. But keep helping out and we'll express our gratitude accordingly!

@seekheart
Copy link
Contributor Author

@paglias it was fun contributing :)

@paglias
Copy link
Contributor

paglias commented Feb 19, 2018

@seekheart great! Sorry for the time it took to merge this in :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pets and Mounts in the Stable need margin updates
5 participants