project migration enhancement, migration guide collateral usage#29
Conversation
… mcp server extension UI
…ister commands to MCP status bar, and enhance migration phases with ccxml/macro/build-dir steps
…into dev_shashank # Conflicts: # src/mcp/idea-mcp-config.ts # src/mcp/idea-mcp.ts # src/migration.ts # src/utilities/utils.ts
…into architecture
| saveProjects(extensionContext); | ||
| } | ||
|
|
||
| export function updateProjectMigrationFolderExceptions(projectInfo: ProjectInfo, folderExceptions: string[]) |
There was a problem hiding this comment.
This is not needed. the setMigrationCheckFolderException above it does this and more! it checks for no duplicates. So this is not needed.
| const projectCCodeUrisToMigrate = projectCCodeUris.filter(uri => !ignoredUriSet.has(uri.toString())); | ||
|
|
||
| const totalFilesafterignoring = projectCCodeUrisToMigrate.length; | ||
| const filesToProcess = projectCCodeUris.filter(uri => !ignoredUriSet.has(uri.toString())); |
There was a problem hiding this comment.
the old naming is better. Logic is the same.
| } | ||
|
|
||
| return relevantLineNumbers.length > 0 ? relevantLineNumbers.map(lineNumber => lineNumber - 1) : [-1]; | ||
| return relevantLineNumbers.map(lineNumber => lineNumber - 1); |
There was a problem hiding this comment.
not sure what this is but I am okay with it.
|
|
||
| Given the local path to the HTML file (downloaded in the migration workflow) and a symbol anchor (the fragment from a Migration Collateral URL, e.g. "CMPSS_configFilterHigh"), returns a structured Markdown block describing the change: old/new function signatures, argument changes, removed/added parameters, and the full diff body. | ||
|
|
||
| Pass anchor "--all" to render the entire report as a single Markdown document. |
There was a problem hiding this comment.
We shouldnt make all an option. it is too big. We will have that for NON MCP usage.
| } | ||
|
|
||
| server.registerTool( | ||
| 'render_migration_guide_section', |
There was a problem hiding this comment.
more clear name. Rendering to MD is okay. but we should call it get_migration_guide_section so the agent is more aware this is not a rendering tool. It gets the right section for it.
| } | ||
| } | ||
| ); | ||
|
|
There was a problem hiding this comment.
We are still missing the TRIGGER for downlaod.
|
|
||
| For every `${MACRO_NAME}` referenced in the applied include paths, check if that macro is defined in the target project. If missing, copy its definition from the source project, replace the source device name in the value with the target device name, and add it to **all build configurations** in the target project. Record each added macro in `c2000-migration.md`. | ||
|
|
||
| > **Example:** Source defines `C2000WARE_DLIB_ROOT = ${COM_TI_C2000WARE_INSTALL_DIR}/driverlib/f28003x/driverlib/`. The universal target starter does not have this macro, so the include path `--include_path="${C2000WARE_DLIB_ROOT}"` would expand to nothing. Add it to the target project as `C2000WARE_DLIB_ROOT = ${COM_TI_C2000WARE_INSTALL_DIR}/driverlib/f28p551x/driverlib/`. |
There was a problem hiding this comment.
instead of f28003x
|
|
||
| **After applying include paths — macro resolution check (required):** | ||
|
|
||
| For every `${MACRO_NAME}` referenced in the applied include paths, check if that macro is defined in the target project. If missing, copy its definition from the source project, replace the source device name in the value with the target device name, and add it to **all build configurations** in the target project. Record each added macro in `c2000-migration.md`. |
There was a problem hiding this comment.
how would we do this?
|
|
||
| | Migration type | `FROM_SDK` | `TO_SDK` | Base URL version | | ||
| |---|---|---|---| | ||
| | F28x → F28x | `C2000Ware_6_00_00_00` | `C2000Ware_6_00_00_00` | `C2000Ware_6_00_00_00` | |
There was a problem hiding this comment.
shouldnt we updgrade to https://dev.ti.com/tirex/content/C2000Ware_26_01_00_00/docs/C2000Ware_26_01_00_00_Migration_Guides/html_pages/MainDriverlib.html
C2000ware: C2000Ware_26_01_00_00
2 participants
No description provided.