mirror of
https://github.com/enso-org/enso.git
synced 2024-11-27 02:55:06 +03:00
1d2371f986
Fixes #7336 in a quick way. Next to the old way of defining groups, the library can just add `GROUP` tag to some entities, and it will be added to the group specified in tag's description. The group name may be qualified (with project name, like `Standard.Base.Input/Output`) or just name - in the latter case, IDE will assume a group defined in the same library as the entity. Also moved some entities from "export" list in package.yaml to GROUP tag to give an example. I didn't move all of those, as I assume the library team will reorganize those groups anyway. ### Important Notes @jdunkerley @radeusgd @GregoryTravis When you will start specifying groups in tags, remember that: * The groups still belongs to a concrete project; if some entity outside a project wants to be added to its group, the "qualified" name should be specified. See `Table.new` example in this PR. * If the group name does not reflect any group in package.yaml **the tag is ignored**. * A single entity may be only in a single group. If it's specified in both package.yaml and in tag, the tag takes precedence. --------- Co-authored-by: Ilya Bogdanov <fumlead@gmail.com> |
||
|---|---|---|
| .. | ||
| automata | ||
| bitmap | ||
| callback | ||
| code-builder | ||
| config-reader | ||
| data-structures | ||
| debug-api | ||
| ensogl | ||
| executor | ||
| frp | ||
| frp2 | ||
| fuzzly | ||
| generics | ||
| json-rpc | ||
| json-to-struct | ||
| launcher-shims | ||
| logging | ||
| macro-utils | ||
| metamodel | ||
| notification | ||
| parser | ||
| prelude | ||
| profiler | ||
| reflect | ||
| shapely | ||
| shortcuts | ||
| text | ||
| types | ||
| web | ||
| zst | ||