-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat : Add the ability to generate sourcemaps from CLI #1826
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Akash <akashsingh2210670@gmail.com>
Signed-off-by: Akash <akashsingh2210670@gmail.com>
… command line arguments Signed-off-by: Akash <akashsingh2210670@gmail.com>
…ionality Signed-off-by: Akash <akashsingh2210670@gmail.com>
… mapping support Signed-off-by: Akash <akashsingh2210670@gmail.com>
…urcemap generation Signed-off-by: Akash <akashsingh2210670@gmail.com>
…osition handling Signed-off-by: Akash <akashsingh2210670@gmail.com>
Signed-off-by: Akash <akashsingh2210670@gmail.com>
Signed-off-by: Akash <akashsingh2210670@gmail.com>
…and YAML line counting Signed-off-by: Akash <akashsingh2210670@gmail.com>
…n Evaluator Signed-off-by: Akash <akashsingh2210670@gmail.com>
I’ve been working on implementing the ability to generate sourcemaps via the CLI, as outlined in this issue. The current implementation tracks and writes the mapping between the source lines and the generated YAML lines. This has taken over 12 hours of work so far, and I’d greatly appreciate any feedback on the approach and implementation details before proceeding further to write tests for it. Since this feature is part of the v1.0 release milestone (due January 31st), I want to ensure we’re on the right track early on. Let me know your thoughts! |
Signed-off-by: Akash akashsingh2210670@gmail.com
1. Does this PR affect any open issues?(Y/N) and add issue references
Fixes #1630
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: