- 05 1月, 2016 2 次提交
-
-
由 Marcin Maciaszczyk 提交于
-
由 Sebastian Florek 提交于
-
- 31 12月, 2015 1 次提交
-
-
由 bryk 提交于
Now raw data is gathered on the backend and rendered on the frontend.
-
- 29 12月, 2015 1 次提交
-
-
由 bryk 提交于
Now variables are in variables.css in frontend directory. Previously they were in assets, which was wrong because it caused copy to production image.
-
- 28 12月, 2015 1 次提交
-
-
由 bryk 提交于
-
- 21 12月, 2015 2 次提交
- 18 12月, 2015 3 次提交
-
-
由 Marcin Maciaszczyk 提交于
-
由 Sebastian Florek 提交于
-
由 Atanas Mirchev 提交于
-
- 11 12月, 2015 1 次提交
-
-
由 Sebastian Florek 提交于
Added check to prevent display of replica set list page when there are no replica sets.
-
- 10 12月, 2015 1 次提交
-
-
由 Marcin Maciaszczyk 提交于
-
- 08 12月, 2015 1 次提交
-
-
由 Marcin Maciaszczyk 提交于
-
- 25 11月, 2015 2 次提交
-
-
由 Marcin Maciaszczyk 提交于
-
由 bryk 提交于
With this change I've gone through all ESLint rules at: http://eslint.org/docs/rules/ and added all of them that I feel make sense to the project. This will allow us to focus on business logic of our code, rather than on style discussions, which are now better guarded thanks to ESLint and clang-format. On the final note: it does not matter what concrete lint rules are enforced (e.g., semicolons or nor). The important part is that they are enforced by a tool and we do not spend time dicussing about them. Addresses: #66
-
- 24 11月, 2015 1 次提交
-
-
由 bryk 提交于
This change reformats all files according to clang-format rules (the same that Angular JS has) and forces the files to comply with the formatting.
-
- 23 11月, 2015 2 次提交
-
-
由 bryk 提交于
The implementation consists of backend code and sample frontend view that dumps the data into an ugly looking table. Subsequent changes will implement frontend so that things look pretty.
-
由 bryk 提交于
This change connects replica set list and detail views and applies RESTful conventions to the API. Now API and app URLs follow RESTful API conventions. This change is also an example of how views hould be connected. See state params and state name exports.
-
- 20 11月, 2015 1 次提交
-
-
由 bryk 提交于
This is a required change because with dot case we cannot reference other modules inside JSDoc `@type` annotations. For example, if you want to reference `@type {./deploy.controller.FooType}` does not work, because the compiler does not know whether `deploy` is a module or `deploy.controller`. Changing dot case to undersocre, camel or dash case solves this problem. I decided to go with underscore case because this is what golang uses (e.g., `foo_test.js`) so we'll have higher similarity of backend and frontend codebases.
-
- 18 11月, 2015 1 次提交
-
-
由 bryk 提交于
This is all frontend boilerplate for the view.
-