This task was deprecated since 16.6.

Changelog: removed

Co-authored-by: James Nutt <jnutt@gitlab.com>

Add missing junit_merge install command

Update cng pipeline setup

Remove flaky test changed warning

Fix sourcing spec helpers

Log junit_merge command

This extends the tailwind_all_the_way.mjs to accept an --only-used
flag.

Also remove the `content` option override from the all_the_way config.

I don't think we need this anymore, we can rely on the conversion script
to decide whether or not we want to parse all the utils.

Tailwind doesn't allow to individually control the styles of borders
(bottom, left, right, top). We use those utils, so let's move them to
our custom list of utility definitions.

Furthermore we make use of the `@layer component` and `@layer utilities`
for our custom component / utility definition, so that tailwind can
properly prune those classes in the future.

Once the vite server starts, we compile tailwind_all_the_way once in
order to generate the css_in_js file.

I cannot wait that we get rid of that file...

This is the first step towards generating all utility classes with
tailwind. The idea behind this is the following:

Parse all utility classes being provided by @gitlab/ui into a JSON
object where each class is represented as something like this:

```
'.bg-gray-10': {
  'background-color': 'var(--gray-10, #fbfafd)',
},
```

We then let tailwind generate all the utilities and compare the class
definitions above with the class definitions in @gitlab/ui. They can
fall into four categories:

- exact matches: The tailwind generated class matches @gitlab/ui 1:1
- potential mismatches: The tailwind generated class mismatches
  significantly. This can be okay or we may need some adjustments to the
  tailwind config.
- hardcoded colors: Some of the utility classes have hard coded colors
  which the conversion script is not able to resolve to a CSS variable.
- safe to use legacy utils: These utils have no overlap with tailwind at
  all. The class names completely differ. This means we can feed the
  definitions above into tailwind, so that tailwind is able to generate
  the classes

As part of the conversion certain aspects are normalized, for example
colors like `#fbfafd` are normalized to `var(--gray-10, #fbfafd)`, but
only if the class name contains `gray-10`.

Furthermore we currently check-in two files that later will be
git-ignored:
1. config/helpers/tailwind/css_in_js.js – containing the css-in-js
   definitions for tailwind to generate the legacy utils with tailwind
2. config/helpers/tailwind/all_utilities.haml – containing a list of all
   utility classes, so that tailwind is able to generate _all utilities_
   and not just the used ones

This reverts merge request !148160

The majority of the docs filenames use underscores instead of dashes.

- Dashes: 72 pages
- Underscores: 1027 pages

We have a similar test for directory names, this expands it to filenames
as well.

Signed-off-by: Rémy Coutable <remy@rymai.me>

This creates the `tailwind_all_the_way` feature flag and lays the
groundwork for what we'll need to take advantage of it:

* GitLab UI utitilies are moved to their own stylesheet so that we can
  easily switch between the legacy library and the Tailwind one.
* We create the "all the way" Tailwind stylesheet and config. These
  compile the `app/assets/builds/tailwind_all_the_way.css` CSS file
  which gets included when the feature flag is enabled. For now, this
  file is unreliable as it requires the second iteration where we'll
  create the proper CSS in Js config for Tailwind to generate our legacy
  utils.
* The Tailwind compiler is updated to compile both Tailwind CSS bundles.

Using named captures makes mappings more readable.
Using file patterns makes source definitions more concise.

Migrate value_streams_dashboard to internal events

- Enable ee/spec/features/remote_development/workspaces_dropdown_group_spec.rb
  even though it's still failing

Do not report cng instance failures

Reduce parallel job count

Run cng tests on all schedule

Use image with git lfs

Add pre-receive hook needed for tests

Improve install script logging

Quarantine conan test in cng

Set application cache setting to 0

Fix needs

Allow local requests for cng tests

Add additional logging for fetching ip address

Remove host assumptions from ip address detection flow

- Add remote dev entries to test.yml
- Fix rubocop warnings

David Dieulivol 创作于 1 year ago ，Lin Jen-Shin 提交于 1 year ago

This will make it easier to wrap the RSpec commands into sections.

When post-processing our CSS with postcss, we can also apply the
tailwind plugin in case one of the files contains `@apply`. We don't
need to do that if the files do not contain `@apply` which will make the
process a lot faster.

Because why not.

This moves autoprefixer from a gem to node. This means we do not
postprocess our CSS with autoprefixer in sprockets, which was executing
JavaScript with `execjs` _and_ a bundled version of autoprefixer, but we
do it directly when compiling our CSS.