Rule: prefer N/xml over DOMParser and XMLSerializer

Open
  • Is something wrong?
#54 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start with the type definitions and Oracle documentation to confirm the N/xml replacement APIs, then read docs/rule-priority.md for the project's priority tiers. Decide how detection handles SuiteScript annotations such as @NScriptType, whether the rule can offer a safe fix, and its default severity and preset placement. Done means these choices are settled and the rule's behavior and placement are specified.

Written by the indexing model from the issue text.

Description

enhancement needs-triage

TODO: add a rule that prefers N/xml over DOMParser and XMLSerializer, which are not available server-side.

Open questions for triage:

  • Confirm against the type definitions and Oracle docs (docs/rule-priority.md tiers) that this is preferable and what the exact replacement APIs are.
  • Detection approach and false-positive risks (e.g. script type via @NScriptType).
  • Whether to offer a fix.
  • Default severity and preset placement.
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
2h 8m
Merged PRs (30d)
64

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nemchik/biome-plugin-suitescript

All issues in nemchik/biome-plugin-suitescript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.