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

[Infra UI] Refactor 'capabilites' to 'metadata'. #25580

Merged
merged 2 commits into from
Nov 20, 2018

Conversation

skh
Copy link
Contributor

@skh skh commented Nov 13, 2018

Summary

Refactors all occurences of "capabilities" in GraphQL and the corresponding container to "metadata". Future work will likely rename some parts of this again, to make it more specific what kind of metadata is handled (metric fields, modules, ...), this is just the first step to get rid of the "capabilities" term.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

- [ ] This was checked for cross-browser compatibility, including a check against IE11
- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
- [ ] Documentation was added for features that require explanation or tutorials

- [ ] This was checked for keyboard-only and screenreader accessibility

For maintainers

The only place that uses the affected GraphQL endpoint was adapted.

- [ ] This includes a feature addition or change that requires a release note and was labeled appropriately


To test:

  • Verify the metrics detail page works, it is the only place using the capabilities/metadata endpoint so far.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Member

@weltenwort weltenwort left a comment

Choose a reason for hiding this comment

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

The node detail page seems to work as before. 👍

"One specific capability available on a node. A capability corresponds to a fileset or metricset"
type InfraNodeCapability {
export const metadataSchema = gql`
"One specific metadata information for a node."
Copy link
Member

Choose a reason for hiding this comment

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

There is something about information always being plural in english. How about "A metadata entry for a specific node" to circumvent that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's better, thank you.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@skh skh force-pushed the infraops-refactor-capabilities-metadata branch from b7e1b5c to 2a63391 Compare November 15, 2018 14:13
@elastic elastic deleted a comment from elasticmachine Nov 15, 2018
@elastic elastic deleted a comment from elasticmachine Nov 15, 2018
@skh
Copy link
Contributor Author

skh commented Nov 15, 2018

jenkins, test this

@elasticmachine
Copy link
Contributor

💔 Build Failed

@skh skh force-pushed the infraops-refactor-capabilities-metadata branch from 2a63391 to 310dd0f Compare November 19, 2018 16:24
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@skh skh merged commit 40960f9 into elastic:master Nov 20, 2018
skh added a commit to skh/kibana that referenced this pull request Nov 20, 2018
* Refactor 'capabilites' to 'metadata'.

* Better language in inline documentation.
skh added a commit that referenced this pull request Nov 20, 2018
* Refactor 'capabilites' to 'metadata'.

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

Successfully merging this pull request may close these issues.

3 participants