Current installation procedure in README.rst and
doc/source/install/installation_contents.rst does not have
installation process of heat-dashboard itself.
I added above procedure by this review request.
Change-Id: I97f7d114c1f1e978286bd218df558ddf5340d901
In future, Heat relevant files(like GUI, api client, policy files, ...)
will be split out from Horizon repository.
But now this repository does not have Heat policy file so I've copied
it from Horizon latest repository.
This review request also includes following changes.
- Added installation procedure document relates to heat_policy.json.
- Modified plugin.sh to install heat_policy.json.
Change-Id: I8dd386e392eb4467b03efd68c7959371d4b9576d
- Heat GUI part
- API wrapper client
- API rest endpoint creator (like api/rest/heat)
According to above changes, I've fixed all unittest
that can work without Heat relevant logic in Horizon.
Change-Id: I7b8c61275e1fef9e27a34d7e65693ee00d07110d
The legacy jobs legacy-horizon-tox-py27dj1* needs to be clean up,
so it is not a good idea to consume them in horizon plugin jobs.
It prevents from pushing them away.
This commit tries to py27dj1* zuulv3 jobs defined in the horizon repo.
Needed-By: I23a95b36e73bb444f94683c801eda11fb1430aa8
Change-Id: I040b35a4830423dce6fa4279882a01b8e88ad5f9
npm dependency packages are installed for js unit tests,
and not necessary in production.
Move all contents from `dependencies` to `devDependencies`
in package.json
Change-Id: I06c7a9b97c2dc6693bb35cee3510c3282d14d6ac
Add .zuul.yaml file to make sure more flexible zuul job controll by
heat-dashboard team members, apart from project-config repo.
We will keep basic & common jobs in project-config repo,
also heat-dashboard repo will have specific jobs like as multi django
ver jobs.
Change-Id: Ia9084b10bf4bb1941e0eb21b51798c2090b459cc
The following changes have been made.
- Test cases for common components and individual resources.
- Setup karma + jasmine test environment.
- Setup eslint environment and rules.
- Code style adjustment to satisfiy eslint rules.
Change-Id: Icb3e48be11beaebc4e410644c62e0df86b345207
To ensure project imports are placed after third party import,
we need to specify application-import-names.
Previously flake8-import-check checks only standard imports or not.
Change-Id: I9beb2105f686dc7d9aebfce8e21c5e182698e2fe
Currently themes machinery works in such way that if we rely on
default theme in our branded theme, we have to include them both into
AVAILABLE_THEMES setting, otherwise default theme assets will be
unavailable and the branded theme assets compilation will fail. On
the other hand, mentioning them both leads to theme picker being
shown - which we would like to avoid (per marketing wish).
SELECTABLE_THEMES setting was added to allow limiting the user facing
themes by configuration.
Closes-bug: #1564543
Co-Authored-By: Ivan Kolodyazhny <e0ne@e0ne.info>
Change-Id: Ic00a9201d2d352685b1089a37a25987b75d6636d
doc8 is a linter for documents and used in openstack-manuals.
It is better to enforce document linters for simple checking.
The current rules are really simple like:
- line length check (80 chars)
- new line at the end of file
Change-Id: I3810df521068ffc97e25a5fc56b72397bf9783bc
py27dj18 currently uses Django 1.10 (from upper-constraints.txt).
The Django version should be specified explicitly.
Change-Id: I23a6dda4da52a0758e2f3e3bff26795c161babb8
After updating code from actual branch we still use old *.pyc files.
It can give an unexpected result, for instance, a lot of tests are
broken due to unknown reasons.
This patch fixes this issue.
Change-Id: I3bdbad9748dc3d94d6d8914156604eab7ad877a0
In reviews we usually check import grouping but it is boring.
By using flake8-import-order plugin, we can avoid this.
This flake8 plugin is already used in tempest.
It enforces loose checking so it sounds good to use.
Note that flake8-import-order version is pinned to avoid unexpected
breakage of pep8 job.
Change-Id: I8ccd05eb70350a2441cc2a4d1eafc09ee690b83b
* Clean up unnecessary vertical quotes at the left side
caused by extra spaces at the beginning of lines.
* Do not use backquotes in the title lines
(ref/run_tests.rst, ref/horizon.rst)
When backquotes are used in the first-level title,
it will be included in the navigation at the top-right corner
https://docs.openstack.org/developer/horizon/contributor/ref/index.html
* Remove duplicated contents:: directive in ref/run_tests.sh.
openstackdocstheme generates the toc by default, so having contents::
directive leads to duplicated toc in a page.
Change-Id: Icc641927ad7cd7a8d79632c64a3ce212f0dc0b64
Much like the themable selects and checkboxes, number spinners
should also be themable.
Standard number spinners are not very customizable. We should use
existing buttons and fonts to add their functionality to allow a
richer experience if desired downstream.
An example of how to customize the spinner was placed in Material.
The example shows how to use flexbox to change layout type from
column to row, change icon order, and how to override the icons.
'autocomplete' needs to be false on this new element, otherwise
the browser will retain and load the last value without actually
triggering any JavaScript events by which we can key on and update
the state of the spinner buttons.
Change-Id: Ifd266cd515a903841e2d28e2f4731879116e3513
Closes-bug: #1598311
_script_i18n.html which tries to access 'jsi18n' url assumes
context['JS_CATALOG'] is populated, but openstack_dashboard test
helper clears it by mocking a context processor.
This leads to a error in rendering templates in unit tests.
Note that template rendering error is caught by a rendering engine
so unit test itself succeeds even when this happens.
Change-Id: I0f5013c4e9ed7b166c527b1aacd0302413948d51
Closes-Bug: #1699509