I just realized that while mepo is really generic, one thing that is "hard-coded" is the @ symbol for the repo:
|
def stylize_local_path(local_path, style): |
|
repo_flag = "@" # Assumed flag for repos |
|
local_list = splitall(local_path) |
|
last_node = local_list[-1] |
|
last_node_list.append(last_node) # maintain a list of last nodes |
|
# Decorate ALL last nodes since we can have nested repos |
|
for item in last_node_list: |
|
try: |
|
index = local_list.index(item) |
|
local_list[index] = decorate_node(item, repo_flag, style) |
|
except ValueError: |
|
pass |
|
return os.path.join(*local_list) |
One question is: should we allow this to be specified say in .mepoconfig? That is, if someone out there is determined to use % instead of @ in their components.yaml then bits of mepo at the moment would not work.
This is very minor, but something to think about.
I just realized that while mepo is really generic, one thing that is "hard-coded" is the
@symbol for the repo:mepo/src/mepo/component.py
Lines 190 to 202 in 5fe9c3d
One question is: should we allow this to be specified say in
.mepoconfig? That is, if someone out there is determined to use%instead of@in theircomponents.yamlthen bits ofmepoat the moment would not work.This is very minor, but something to think about.