-
Notifications
You must be signed in to change notification settings - Fork 35
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
Ui for normalize metadata #2278
Conversation
@brylie I've done fetch organization data via collection helper. But I have an open question:
|
One idea, would be to display the related Organization somewhere on the API Profile page (e.g. in the header). That way, we can use the collection helper to retrieve the Organization document, and display the organization name. In effect, we are fully removing the Organization from the Metadata feature/view. @Nazarah and @bajiat, what are your thoughts? Do we have some time available to add the Organization details to the API Profile wireframe? |
@brylie We can leave it as Enhancement. Now I implemented it with minimal trigger actions. |
metadata/collection/schema.js
Outdated
@@ -24,10 +24,13 @@ ApiMetadata.schema = new SimpleSchema({ | |||
}, | |||
'contact.phone': { | |||
type: String, | |||
// TODO: used constant contactPhone | |||
regEx: /^[0-9-+()/\s.]+$/, |
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.
Please describe this regular expression in plain English. We are currently reviewing regular expressions, so we can provide human friendly error messages.
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.
After merging 2276 PR I will replace it to constant
// Make sure API metadata doesn't exists | ||
if (!apiMetadata) { | ||
// Create a new document | ||
ApiMetadata.insert({ apiId }); |
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.
Why do we need to create a dummy document?
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.
Lets try to find a solution that doesn't create 'empty' documents.
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.
It isn't empty. You can it perceive like a container for displaying organization information.
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.
Ah, I think I see the problem. Rather than creating an empty document, just so we can use collection helper from the API Metadata collection, simply use the existing Apis.organization() helper.
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.
Hm. I need to think about it. I have an idea
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.
Kool. Remember to just keep it simple.
@brylie If API Metadata doesn't exists, it will be look so: |
But we need to think up something about text "No Metadata found".
|
@marla-singer lets just see if we can move the organization details to the API Profile. That would sidestep this whole issue. |
c15757f
to
128df23
Compare
agree with @brylie about showing organization information in API profile header. |
I think it is ok to show organization name in the API profile header. Long term I think APIs should either be added by an organization or a person. This would mean that we could namespace the APIs with either username or organization name. This probably requires rethinking how we add APIs. But if there are any other details in the Metadata tab for organization, I'm not sure they should be added anywhere else than Metadata. Unless you have a concrete suggestion where we would have room for more details than organization name. If the Metadata tab contains information about organization, is it really necessary to show "No metadata found". Even though technically the remaining information comes from Metadata document, does the user care about that? |
@marla-singer I just got approval from @bajiat to simply add the organization name to the API Profile page, in a way that we see fit. We will get review from @bajiat and @Nazarah when we have a working example. |
@marla-singer : can we reposition the star-ratings a bit down and then position Organization data there? |
The API profile header is fact-laden 😕 |
@bajiat Remove or not Organization block from Metadata tab at all? |
@marla-singer Go ahead and remove organization from Metadata |
@brylie Ready for review |
Closes #2185
Closes #2064
Closes #855