This repository has been archived by the owner on Dec 10, 2021. It is now read-only.
Using Jinja params every where and not just in raw query views #386
Comments
ktmud
pushed a commit
to ktmud/superset-ui
that referenced
this issue
Apr 22, 2020
…rset#386) Bumps [@vx/responsive](https://github.com/hshoff/vx) from 0.0.194 to 0.0.195. - [Release notes](https://github.com/hshoff/vx/releases) - [Changelog](https://github.com/hshoff/vx/blob/master/CHANGELOG.md) - [Commits](airbnb/visx@v0.0.194...v0.0.195) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
|
The codebase on this repo has been moved to the main Apache Superset repo, and consequently the repo is in the process of being archived. See the Superset Improvement Proposal for details: apache/superset#13013 . While all currently open issues and PRs will be closed, we encourage you to reopen this issue on the main repo if it is still relevant. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
No, just a "nice to have"
Describe the solution you'd like
Given that I am creating a Superset chart
when I input a custom y axis label string value
then I will use a Jinja parameter I previously set
Describe alternatives you've considered
Writing it in
Additional context
It'd be cool to use Jinja parameters every where and not just queries, I tried it out but it doesn't seem to work is this possible yet? Thank you!
The text was updated successfully, but these errors were encountered: