Repository navigation
feat(lockless rendering): prepare for azldev updates to allow lockless rendering - #20006
Dan Streetman (ddstreetmicrosoft) wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the configuration include and placeholder changes.
No open issues 🎉
What changed in this PR
Prepares the base project for upcoming azldev support for lockless rendering without implementing that support yet.
Changes:
- Adds
upstream-commits/*.tomlto the base project's configuration includes. - Adds an empty
lockless-components.txtplaceholder.
| File | Description |
|---|---|
lockless-components.txt |
Adds an empty placeholder for lockless-rendering preparation. |
base/project.toml |
Includes upstream-commit TOML files in the base configuration. |
Review effort: Balanced
| # | ||
|
|
||
| includes = ["comps/components.toml", "images/images.toml", "images/images.tests.toml"] | ||
| includes = ["upstream-commits/*.toml", "comps/components.toml", "images/images.toml", "images/images.tests.toml"] |
There was a problem hiding this comment.
question(blocking): I don't see that we have an upstream-commits folder. Just confirming that that includes can handle non-existent files and directories?
There was a problem hiding this comment.
as far as i can tell it does, running update and render works fine.
|
/azp run |
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. |
…l files work on azldev to transition off using 'lock' files involves moving component upstream commit configuration into separate toml files, which need to be included during toml parsing. this adds a directive to include those files using a glob pattern. since there are currently no matching toml files, this is currently a no-op.
work on azldev to remove use of 'lock' files will transition individual components from using a 'lock' file to 'lockless' rendering. as this is strictly a transitional process, a temporary file named 'lockless-components.txt' at the same level as the 'azldev.toml' file will be used to record which components should use 'lockless' rendering; any not in the file will continue to use 'lock' file rendering. as this file currently contains nothing, this is currently a no-op. after all components are transitioned to 'lockless' rendering, and azldev is updated to remove support for 'lock' files, this file will no longer be needed and should be removed.
3bdf7a3 to
628c51f
Compare
|
no-change force push to correct my commit subject that was using |
|
/azp run |
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. |
Add 2 no-op commits in preparation of adding azldev support for lockless rendering.