Skip to content

Feature/visibility checks2#1718

Merged
marla-singer merged 21 commits intodevelopfrom
feature/visibility-checks2
Oct 10, 2016
Merged

Feature/visibility checks2#1718
marla-singer merged 21 commits intodevelopfrom
feature/visibility-checks2

Conversation

@jykae
Copy link
Copy Markdown
Contributor

@jykae jykae commented Oct 7, 2016

Closes #1624
Closes #1673
Closes #1686

Replaces #1697

@jykae jykae added this to the Sprint 32 milestone Oct 7, 2016
@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 7, 2016

@marla-singer this replaces #1697 could you review? As part of the process, when this gets merged, the old can be closed.

@marla-singer
Copy link
Copy Markdown
Contributor

@jykae Check only the tags work or all visibility feature work?

@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 7, 2016

@marla-singer my work is checks & tags, but take also overall view of the feature.

Have a nice weekend, I return to this on Monday, if anything.

Copy link
Copy Markdown
Contributor

@marla-singer marla-singer left a comment

Choose a reason for hiding this comment

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

Finished. Found some code style remarks and unexpected renaming css class

{{ api.name }}
{{> viewApiStatus api=api width="0.4" }}
</h1>
{{#unless api.isPublic }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please add a space between # and unless

{{ api.getApiManagersByName }}
</span>
<p class="api-card-description">
{{#unless api.isPublic }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please add a space between # and unless

{{_ "catalogueTable_added" }}
{{ api.relativeCreatedAt }}
</i>
{{#unless api.isPublic }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Space between # and unless

margin-bottom: 1.87em;

.icon-indicator {
.api-status-color {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why did you change it? Because of it the status indicator has wrong place:
Found:
joxi_screenshot_1475848265426
Expected:
joxi_screenshot_1475848243115
Or add class "pull-right" after variable "className" in this line
https://github.com/apinf/platform/blob/develop/apis/client/view/status/status.js#L23

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I like the pull-right approach. Simple, and doesn't require any new CSS/Less.

Copy link
Copy Markdown
Contributor Author

@jykae jykae Oct 10, 2016

Choose a reason for hiding this comment

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

@marla-singer pull-right fixes catalogue grid view but in API header:

nayttokuva 2016-10-10 kello 14 46 31

I'd give styling for indicator outside status component. Because alignment might not always be the same. Or is it fine on top corner of text, and not vertical-center?

Copy link
Copy Markdown
Contributor

@marla-singer marla-singer Oct 10, 2016

Choose a reason for hiding this comment

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

@jykae I checked on nightly. Yes, pull-right doesn't work as expected. So change style like

.api-status-color, .icon-indicator { ... }

@marla-singer
Copy link
Copy Markdown
Contributor

marla-singer commented Oct 7, 2016

@jykae Api owner doesn't watch the others public apis. Screenshots:

  1. Go to catalog, pick the other public api.
    joxi_screenshot_1475848537196
  2. Found result: Forbidden
    joxi_screenshot_1475848566195

Also it looks like you forgot add i18n tag to json file.

@marla-singer
Copy link
Copy Markdown
Contributor

marla-singer commented Oct 7, 2016

@jykae As for me the red rectangle part looks very strange. That's not obvious how i can use it?
joxi_screenshot_1475849268120

@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 10, 2016

@marla-singer Thanks for review, other things look fine founds, but the last one is not clear.

Authorized users part is @brylie 's work from another PR. Already accepted.
Only API owners & admins are able to view/edit API when it's private + authorized users can view
It is used to give single users permissions to view API even when API is globally marked Private.
@marla-singer Do you think it would need help text of some sort about usage? I think we can mark that as enhancement task.

@marla-singer
Copy link
Copy Markdown
Contributor

@jykae Yes, I think It should be some message to describe the purpose of this field as sentence you wrote me above "It is used to give single users permissions to view API even when API is globally marked Private."
Okay, enhancement task sounds good too.

@brylie
Copy link
Copy Markdown
Contributor

brylie commented Oct 10, 2016

@jykae would you add the help text where @marla-singer suggests? Otherwise, how near is this PR to being merged?

@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 10, 2016

@brylie @marla-singer Ok, I add suggested help text. Working on this now.

@brylie
Copy link
Copy Markdown
Contributor

brylie commented Oct 10, 2016

@jykae thanks. What is the estimate of time to complete?

@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 10, 2016

@brylie 12.5 mins

@brylie
Copy link
Copy Markdown
Contributor

brylie commented Oct 10, 2016

Perfect!

@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 10, 2016

@brylie sorry went bit over estimate, @marla-singer please review changes

"apiSettings_visibilityPanel_title": "Visibility",
"apiSettings_visibility_heading": "Change API visibility",
"apiSettings_visibility_text": "Make this API private or public",
"api_settings_visibility_authorizedUsers": "Give single users permissions to view API even when API is globally marked Private.",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Rename api_settings to apiSettings as above

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@marla-singer
Copy link
Copy Markdown
Contributor

@jykae api-indicator looks bad with class pull-right 😟
joxi_screenshot_1476105322244

Please remove class 'pull-right' and return '.icon-indicator' class in grid.less
It's almost ready to merge. Just fix css style

Also these doesn't have any help text. Maybe you add like on screenshot? It's just text in <p> tag after <h3> tag
joxi_screenshot_1476105692845

@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 10, 2016

@marla-singer sorry, I don't know what you mean with "return '.icon-indicator' class in grid.less"

@marla-singer
Copy link
Copy Markdown
Contributor

@jykae
Copy link
Copy Markdown
Contributor Author

jykae commented Oct 10, 2016

@marla-singer ok, done. I don't know how that dropped out.. :) Possibly because friday afternoon.

@marla-singer
Copy link
Copy Markdown
Contributor

Merging

@marla-singer marla-singer merged commit 3704e5c into develop Oct 10, 2016
@marla-singer marla-singer deleted the feature/visibility-checks2 branch October 10, 2016 13:47
@bajiat
Copy link
Copy Markdown
Contributor

bajiat commented Oct 10, 2016

thanks to both @jykae and @marla-singer

@brylie brylie modified the milestones: Sprint 33, Sprint 32 Oct 11, 2016
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.

4 participants