Run configuration improve.
Hi! I was working with Fleet since august and i found a little problem. When you have a run.json file in a folder with a deep greater than 4, fleet is not available to sow you the run button, and there is no other way to use that run configuration.
Example:
workspace_dir
--Sub folder 1
----Sub folder 2
------Sub folder 3
--------.fleet
-----------run.json <--- this one dont gives you a way to click the run button
----.fleet
------run.json <--- but this one does.I try my best to explane it, please ask if it is not clear.
Other improvement is that the name of the configuration must be the key to the run configuration because that way you can reduce colapse the run configuration, for a compact view of it, because if you have 20 run configurations it gets unreadable. With this new way of naming the run configuration, you can see also the run button at the left hand improving the actual behavior of it that gets annoying when you colapse the run config, and the button disappears.
Now:
{
"configurations": [
{
"name": "Local Lambda Execute",
"type": "python",
"environment": {
"PYTHONUNBUFFERED": "1",
"PYTHONPATH": "$USER_HOME$"
},
"file": "$PROJECT_DIR$\\main.py",
"arguments": [
""
]
}
]
}
Sugested:
{
"configurations": {
"Local Lambda Execute": {
"type": "python",
"environment": {
"PYTHONUNBUFFERED": "1",
"PYTHONPATH": "$USER_HOME$"
},
"file": "$PROJECT_DIR$\\main.py",
"arguments": [
""
]
}
}
}Here is an example:
The button disappears.
A better visualization:
And the play button can be here:
Thanks for your time.
Please sign in to leave a comment.
Hi FeraxHp! Thank you so much for the report and your suggestions! It is very interesting and valuable! I have filled corresponding requests for it. Please feel free to vote and follow them for updates:
FL-24149 Run configuration is not detected from run.json file with a deep greater than 4
FL-24148 Better representation of collapsed run configurations in run.json
Thank you very much!
Hi FeraxHp!
I've tried to reproduce your issue regarding the run icon not being shown in deeply nested files but failed to do so.
Can you tell me what type of configurations you've experienced this with, or even better, provide me a minimal example project where you see the issue? You can attach it to this issue: FL-24149
Thank you!
Hi Bernhard Geisberger , my project is running with a lot of sub propjets. and that's make to fleet get in trouble, this is a simple view of how my project is configured.
As you can see, fleet don't detect some of the run.json, but if i open they individually, it does detect it.
Thanks for your time.