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

Tab title will update according to the automation page #653

Merged
merged 4 commits into from
Oct 29, 2020

Conversation

rathorevaibhav
Copy link
Contributor

@rathorevaibhav rathorevaibhav commented Oct 28, 2020

Summary

The automation title will be appended to the title of the website. Also added environment variables for:

  1. App name
  2. Page title

@rathorevaibhav rathorevaibhav self-assigned this Oct 28, 2020
@rathorevaibhav rathorevaibhav linked an issue Oct 28, 2020 that may be closed by this pull request
.env.example Outdated
@@ -1,3 +1,5 @@
REACT_APP_API_PREFIX=""
SENTRY_DSN=""
REACT_APP_GLIFIC_API_PORT=4000
REACT_APP_APPLICATION_NAME=""
Copy link
Contributor

Choose a reason for hiding this comment

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

@rathorevaibhav why do we need an app name?

Copy link
Contributor Author

@rathorevaibhav rathorevaibhav Oct 28, 2020

Choose a reason for hiding this comment

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

hey @kurund I made these fields editable from env so that if needed, SaaS providers who extend Glific can rename it.

For example, like Tides, we can have App name set to "Tides" instead of "Glific". It's just so that we provide flexibility to extend the framework. If there's nothing set, the default value will come in which is "Glific". Let me know if this is making sense.

.env.example Outdated
@@ -1,3 +1,5 @@
REACT_APP_API_PREFIX=""
SENTRY_DSN=""
REACT_APP_GLIFIC_API_PORT=4000
REACT_APP_APPLICATION_NAME=""
REACT_APP_PAGE_TITLE=""
Copy link
Contributor

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 define title as env variable?

@kurund kurund added this to the v0.6.0 milestone Oct 28, 2020
@rathorevaibhav rathorevaibhav requested a review from kurund October 29, 2020 14:40
@rathorevaibhav
Copy link
Contributor Author

@kurund this is ready for review again

Copy link
Contributor

@kurund kurund left a comment

Choose a reason for hiding this comment

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

Looks good!

@kurund kurund merged commit 304d90f into master Oct 29, 2020
@kurund kurund deleted the feature/title-change-on-automations branch October 29, 2020 18:43
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.

Showing the automation flow title in the tab
2 participants