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

Add: documentation links for data sources #1381

Closed
wants to merge 2 commits into from

Conversation

washort
Copy link

@washort washort commented Nov 9, 2016

Add a customizable link to documentation for a data source, defaulting to the reference docs for the query language for that source.

@@ -110,7 +110,7 @@ <h4 class="modal-title">Query Archive</h4>
<span class="text-muted">Data Source</span>
<select ng-disabled="!isQueryOwner" ng-model="query.data_source_id" ng-change="updateDataSource()"
ng-options="ds.id as ds.name for ds in dataSources"></select>

<a ng-href={{dataSource.doc_url}}>{{dataSource.type_name}} documentation</a>
Copy link
Member

Choose a reason for hiding this comment

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

can you add a screenshot of how it looks like?

Copy link
Member

Choose a reason for hiding this comment

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

also worth showing only if the url isn't empty.

Copy link
Author

Choose a reason for hiding this comment

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

screenshot from 2016-11-11 11-38-55

Fixed so that it should only show when doc_url is present.

@@ -110,7 +110,7 @@ <h4 class="modal-title">Query Archive</h4>
<span class="text-muted">Data Source</span>
<select ng-disabled="!isQueryOwner" ng-model="query.data_source_id" ng-change="updateDataSource()"
ng-options="ds.id as ds.name for ds in dataSources"></select>

<a ng-if="dataSource.options.doc_url" ng-href={{dataSource.options.doc_url}}>{{dataSource.type_name}} documentation</a>
Copy link
Member

Choose a reason for hiding this comment

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

As I'm not sure how I feel about this, can you hide it behind a feature flag (with default being off)?

(check how I did it for the Manage Permissions button)

Thanks.

Copy link
Author

Choose a reason for hiding this comment

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

Feature flag added.

@arikfr arikfr changed the title Documentation links for data sources Add: documentation links for data sources Nov 15, 2016
@arikfr
Copy link
Member

arikfr commented Nov 24, 2016

Coming to thin of it -- why do we need this as a configuration value for each data source?

@washort
Copy link
Author

washort commented Dec 22, 2016

The reason for configuration values is so that individual data sources can link to data-specific docs rather than just the language reference. (Or to the version of the docs matching the backend DB version, etc.)

@washort washort force-pushed the data-source-docs branch 2 times, most recently from 4a4e489 to 745cde7 Compare January 27, 2017 16:26
@rafrombrc
Copy link

Hi! Just following up on this. We'd really like to get this deployed for our local installation within the next week. Is there a chance of getting this PR merged upstream soon, or should we add it to our own fork for now?

Thanks for your attention!

@arikfr
Copy link
Member

arikfr commented Feb 10, 2017

Let me review this again on Sunday and get back to you.

@arikfr
Copy link
Member

arikfr commented Feb 13, 2017

I don't want to make it hard on you to maintain your fork, but on the other hand don't feel 100% with merging this. As even when it's behind a feature flag, it introduces code that we will have to maintain that won't benefit the general users population.

Let's keep this on your fork for now, and if we see it makes syncing with upstream a hassle, will revisit to think what we can do about this.

How's that sound?

@washort
Copy link
Author

washort commented Feb 13, 2017

We're always going to have some stuff that needs to be in our own fork. I don't think this will be a burden for now. Thanks for having a look.

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.

3 participants