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

Labels on top #4286

Merged
merged 47 commits into from
Jul 14, 2015
Merged

Labels on top #4286

merged 47 commits into from
Jul 14, 2015

Conversation

alonsogarciapablo
Copy link
Contributor

No description provided.

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@@ -267,9 +267,9 @@ def admits_more_torque_layers?
torque_layers.length >= 1 && is_table_visualization? ? false : true
end

# TODO: We need to allow more than one `tiled` layer now
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This will be fixed in #4256. @Kartones, you can create a PR against this branch (labels-on-top).

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@@ -466,32 +472,6 @@ cdb.admin.Layers = cdb.geo.Layers.extend({
saveLayer(layers.at(count));
},

/**
Copy link
Contributor Author

Choose a reason for hiding this comment

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

layers have an order attribute, which is updated every time a new layer is added to the collection. Unless I'm missing something, I think we can get rid of this custom reset and assume layers are ordered.

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

…dropped.

This way the order of layers gets re-calculated correctly.
@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@alonsogarciapablo
Copy link
Contributor Author

This should be now ready to be merged! \o/

@xavijam would you mind taking a look at it? Thanks, thanks and thanks!

@@ -69,7 +69,6 @@ def render_auth_users_data(user, referrer, subdomain, referrer_organization_user
email: user.email,
organization: Carto::Api::OrganizationPresenter.new(user.organization).to_poro,
base_url: user.public_url,
feature_flags: user.feature_flag_names
Copy link
Contributor

Choose a reason for hiding this comment

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

oh! why?

Copy link
Contributor

Choose a reason for hiding this comment

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

ping @Kartones

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Part of this PR is removing this temporary hack and this line was added then.

Copy link
Contributor

Choose a reason for hiding this comment

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

No idea :/

Copy link
Contributor

Choose a reason for hiding this comment

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

Have you checked everything is working properly? If so 👍.

@xavijam
Copy link
Contributor

xavijam commented Jul 13, 2015

And, have you checked google basemaps (under google_maps flag) are working properly?

@alonsogarciapablo
Copy link
Contributor Author

Yes! Google basemaps work 👍

@xavijam
Copy link
Contributor

xavijam commented Jul 13, 2015

In that case 🇬🇧

@alonsogarciapablo
Copy link
Contributor Author

Thanks @xavijam!

@alonsogarciapablo alonsogarciapablo changed the title [WIP] Labels on top Labels on top Jul 14, 2015
@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

@Cartofante
Copy link
Collaborator

Frontend tests were OK 👍 (details)

alonsogarciapablo added a commit that referenced this pull request Jul 14, 2015
@alonsogarciapablo alonsogarciapablo merged commit 83f4709 into master Jul 14, 2015
@alonsogarciapablo alonsogarciapablo deleted the labels-on-top branch July 14, 2015 07:53
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.

None yet

5 participants